apple/container

Try Apple's container CLI. I moved a project of mine from colima+docker to it relatively easily, a couple of weekends ago. https://github.com/apple/container

This looks nice, but on mac you can virtualise really easily into microvms now with https://github.com/apple/container . I've built my own cli that runs the agent + docker compose (for the app stack) inside container for dev and it's working great. I love --dangerously-skip-permissions. There's 0 benefit to us whitelisting the agent while it's in flight. Anthropic's new auto mode looks like an untrustworthy solution in search of a problem - as an aside. Not sure who thought security == ml classification layer but such is 2026. If you're on linux and have kvm, there's Lima and Colima too.

The only big noticeable issue for me was building a large enterprise images (like Splunk). This issue was fixed [1]. Other than that I have not seen any issues with IO or performance. Running Splunk/OpenSearch/ElasticSearch, some performance tests, enterprise software written in Go (building for arm64/amd64). No issues at all. 1. https://github.com/apple/container/issues/68

i've been using a sort of version like this... using the apple container fw. http://github.com/apple/container have you looked into that?

They barely just released Containerization Framework[0] and the new container[1] tool, and they are already scheduling a kneecapping of this two years down the line. Realistically, people are still going to be deploying on x64 platforms for a long time, and given that Apple's whole shtick was to serve "professionals", it's really a shame that they're dropping the ball on developers like this. Their new containerization stuff was the best workflow improvement for me in quite a while. [0] https://github.com/apple/containerization [1] https://github.com/apple/container

ICYMI: Apple's new native containers start in ~100ms and have better security. I updated to Tahoe just for this. And it's open-source: https://github.com/apple/container It's not really supported before Tahoe, presumably due to required hypervisor support.

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

Thanks for the info kdrag0n! Big fan of OrbStack; good call out on dynamic memory. If the guest image has /sbin/init, we use that. We'd recommend using a base image for the guest that includes systemd. ie: https://github.com/apple/container/blob/main/docs/container-machine.md#bring-your-own-container-machine-image

Hi Brandon! Have you tried Apple's container CLI[0]? I'm still mostly using OrbStack, but container gives me some hope for the future that Apple cares about this experience. [0]: https://github.com/apple/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_.

Is this new? I thought we had this already In my testing (iirc) filesystem performance was not good enough to be usable with node/rust dev where lots of small files get stat-ed update: what's new is the `container machine` subcommand. I went to test it out, but container failed to run at all for me: https://github.com/apple/container/issues/1681

I had to abandon Apple MacOS container because it has so many issues with networking and DNS. I'm looking forward to try it again if they can get it fixed. https://github.com/apple/container/issues?q=is%3Aissue%20state%3Aopen%20dns