Live data from Hacker News

macOS Container Machines

github.com

241–250 of 457 posts

Re: macOS Container Machines

#241

This is all fine and dandy, but where are the native Darwin Jails Apple? Still scared that people will filling whole rooms of Mac Minis if you allow them to have multiple macOS containers and not only up to two fat VMs per machine?

[Replied to wrong comment]

Re: macOS Container Machines

#242

This is all fine and dandy, but where are the native Darwin Jails Apple? Still scared that people will filling whole rooms of Mac Minis if you allow them to have multiple macOS containers and not only up to two fat VMs per machine?

sandbox profiles?

Re: macOS Container Machines

#243
post #241

This is all fine and dandy, but where are the native Darwin Jails Apple? Still scared that people will filling whole rooms of Mac Minis if you allow them to have multiple macOS containers and not only up to two fat VMs per machine?

[Replied to wrong comment]

That's totally unrelated to what I wrote

Re: macOS Container Machines

#244
This is pretty cool - being able to bring your own container machine image goes a long way to helping it's adoption.

I started using Colima a couple of years ago because I got bored of how bad Docker Desktop was and just started using the CLI / the "Services" tool window in whatever Jetbrains IDE I was using at the time anyway. I can't see myself moving away from it any time - having multiple profiles is an absolute winner of a feature for me there, but maybe the next time I set up a Mac from scratch I'll have a play with this.

Re: macOS Container Machines

#245

This is all fine and dandy, but where are the native Darwin Jails Apple? Still scared that people will filling whole rooms of Mac Minis if you allow them to have multiple macOS containers and not only up to two fat VMs per machine?

sandbox profiles?

macOS sandboxing is deliberately limited just enough to prevent anyone from truly implement Darwin-on-Darwin containers. People have been discussing about this for a while, see https://github.com/apple/container/discussions/611

In general I understand the rationale behind Apple's decision. They sell hardware, and there's real demand for macOS on servers to run build jobs and other Mac-only tools. Giving you the ability to run multiple containers on a single Mac would end up turning a 10 Mac Mini order into a 2 Mac Minis order for most people. Rest assured, even if it would be technically possible they'd find a way to cap it somehow via the EULA or whatever

Re: macOS Container Machines

#247

Why did they have to invent their own solution instead of just shipping docker or an equivalent clone ?

Isn't docker on mac os still a large preallocated linux VM that runs the containers inside itself? With this maybe you can separate them.

Re: macOS Container Machines

#248

Python binary wheels now have to be built for aarch64 for them to work inside the container, unless they are built using the corresponding build system while installing. It is not common for python binary libs to publish arm64 binary wheels, as most often they target amd64.

Isn't that just expected for modern macOS devices? They have been on arm64 for 6 years now.
Post reply on HN