Badabinski comments on macOS 26 introduces the Containerization Framework: "enables developers to create, download, or run Linux container images directly on Mac"

[–] Badabinski@kbin.earth 2 points 1 year ago (2 children)

I'm not sure. To me, the most interesting thing is that each container gets its own VM. I don't know if podman does that or not. I'd guess not, since CoreOS isn't the lightest OS around (I've used CoreOS and Flatcar extensively at my job and it's a lil chunky as far as immutable container host OSes go).

permalink

fedilink

source

parent

hideshow 2 child comments

[–] pogodem0n@lemmy.world 3 points 1 year ago (1 child)

What would be the use case for each container getting its own VM?

permalink

fedilink

source

parent

hideshow 1 child comment

[–] Badabinski@kbin.earth 2 points 1 year ago* (last edited 1 year ago)

Each VM can be sized appropriately for the demands of the container. With docker desktop, you can't have a container use all of your system cores without making the VM have access to all of your cores all the time always. One of the biggest benefits (imo) of running containers on a Linux workstation is that if you don't define a CPI limit, a container can use all the compute/memory on your system. You just can't do that with Docker desktop. This also affects multi threaded container builds when you're using buildkit.

Being able to spin up a vm to build a container with all cores accessible to it, and then run the actual container with a smaller number of cores would make container builds so much faster.

EDIT: I've looked, and it appears that podman desktop also does 1 big VM, rather than having 1 VM per container.

permalink

fedilink

source

parent