Zenbleed - Hackdot

Re:Zenbleed by stingraycharles on Tuesday July 25, 2023 @01:26AM (#36858303)

Isn’t the typical solution here to pin each VM to certain CPUs / cores?

[ Parent | on HN ]

Re:Zenbleed by tempaccount420 on Tuesday July 25, 2023 @06:09AM (#36860184)

That's not very convenient. I want docker to be able to use all my cores when I build an image.

[ Parent | on HN ]

Re:Zenbleed by petters on Tuesday July 25, 2023 @09:20AM (#36861789)

Docker is not a VM. It uses the same kernel as the host

[ Parent | on HN ]

Re:Zenbleed by t-3 on Tuesday July 25, 2023 @10:59AM (#36863275)

Only on Linux. On other systems it's a VM.

[ Parent | on HN ]

Re:Zenbleed by tempaccount420 on Tuesday July 25, 2023 @01:33PM (#36866094)

Thanks, that's what I meant.

[ Parent | on HN ]

Re:Zenbleed by cbzbc on Tuesday July 25, 2023 @03:26PM (#36868020)

That depends on the docker runtime.

[ Parent | on HN ]

Re:Zenbleed by tvink on Tuesday July 25, 2023 @09:56AM (#36862278)

Even if we pretend docker is a VM, building an image can happen on as many cores as you like in this hypothetical, it's the running of it that should be restricted.

[ Parent | on HN ]