container

You missed the point by focusing on the wrong part (containers) instead of the part that's relevant (kill darwin CLI userland). Imagine the only scriptability you get for the OS is Automator or Shortcuts, https://github.com/apple/container is at best an API at worst a GUI app and certainly not a CLI, and that's it. macOS is MacOS (pre-X). Or iOS-like. Terminal.app spawns a sandboxed Linux microvm. You never see the host from a shell. Dear colima can't even _exist_.

and they have a first-party one now as well https://github.com/apple/container

i know what you mean; just in case you hadn't seen this (which is recent) https://github.com/apple/container

Apple Container is an interesting work in progress: https://github.com/apple/container

There is a name collision on MacOS where MacOS also provides containers [1] [1] https://github.com/apple/container

How would this be different from Apple's recently launched "container" utility? https://github.com/apple/container

> It's just a linux vm running normal docker engine OCI compatible, but not docker https://github.com/apple/container/blob/main/docs/technical-... Actually makes use of Virtualization.framework mentioned above.

> require you to run the agent on your Mac instead of in a Sandbox You don't have to! All recent Macs come with nearly zero perf cost virtualization. You can easily run Mac or Linux VMs assuming same architecture. Use it all the time for development and whatever. Use Tart [1] or VirtualBuddy [2], both open-source, for a packaged solution. Or in the spirit of this post, vibe code your own wrapper around the OS API [3] More recently, there are also Apple containers [4] [1] https://tart.run/ [2] https://github.com/insidegui/VirtualBuddy [3] https://developer.apple.com/documentation/virtualization [4] https://github.com/apple/container

Neat, could it leverage https://github.com/apple/container

It claims to be backed by (and require) apple/containers(1) which "consumes and produces OCI-compatible container images" so if all that is true .... yes! 1) https://github.com/apple/container

Traditional containers like docker desktop need a vm to run its each container. So all container you spin up is store in this always on shared Linux kernel.apple introduced a opensource container project that creates tiny, light weight vm for each of the container you spin up, so when container stopps vm stops.This uses macos virtualisation framework(inbuilt mac os hyperviser{like virtual box, VMware,parallels etc} for M series) , vmnet framework (networking, how processes inside vm will connect to outside world), xpc(cross process communication,using it inter software process communicates with each other). But one question so if this new method of running docker images with each having its own vm, how buildkit will work because it needed to be in kernal environment to build your image and there is no shared vm linux environment alrea

I am skeptical there are many real use cases that require native macOS not arbitrary unix. For files, use a readonly mount https://github.com/apple/container/blob/main/docs/how-to.md#... (ie. /path:ro)

recommend converting to https://github.com/apple/container

I am not (purposefully) granting them the benefit of the doubt. In my comment I simply noted that the comments there are extremely anti-Apple yet without any solid arguments behind them, and I also noted that the whole thing is just because of an APFS flag which could be fixed from Asahi's side. The main reason I made the comment is because I am shocked at how poorly backed the arguments are. As for Apple not helping the Linux team, why would they, or any major OEM? Apple is perfectly happy with https://github.com/apple/container