With colima I can run AMD64 (x86) Linux containers in my Arm64 too. I think this is strictly for Arm64 Linux VMs, or is there some way to run x86 with this too?
Rosetta should be supported
Not for long!
macOS Container Machines
151–160 of 457 posts
Re: macOS Container Machines
#152With the BUILD and WWDC 2026 announcements, it is the Year of Linux Containers Desktop.
Which for many folks is good enough for what they are doing, thus the status quo of desktop platforms will hardly change for current form factors.
Re: macOS Container Machines
#153Earlier quoted context omitted.
I'll defend, not cringe for everyone. Daily driver is a 6yo, 32Mb mbp and it might not scream like an M5 or have the miraculous power draw of an M5, it gets my job done. One nice thing is x86 containers run natively: I run most of my $work landscape which is 40 or 50 k8s pods on top of Kind, which is itself a plain container. That mirrors my prod. That plus slack, zoom, ff with scores of tabs, etc. all while building…
That is a far more useful reply than the GP comment. If they had stated something similar I don’t think they would’ve been downvoted.
Poe's Law and all that, but I was trolling/shitposting.
Re: macOS Container Machines
#154To clarify a few comments here: this is not only OCI containers: container machines add support for persistence and filesystem mounting, making container machines a great lightweight Linux environment for developers using macOS. More details here: https://developer.apple.com/videos/play/wwdc2026/389
> ... highly integrated Linux environment that works seamlessly on your Mac. ...
Which kernel is running, and is it hosted in hypervisor.framework, as is done with UTM (when not using the qemu mode)?
Re: macOS Container Machines
#155Earlier quoted context omitted.
Isn't the Windows subsystem for Linux (the reference there) also a VM?
Only WSL2; WSL1 was an actual subsystem.
WSL 1 is long gone for all practical purposes, yet it still dominates conversations.
Also everyone on FOSS gets it wrong, WSL wasn't a subsystem like classical Windows NT ones.
It was based on Drawbridge research using picoprocesses, a new approach for library OSes.
https://learn.microsoft.com/en-us/archive/blogs/wsl/pico-pro...
Re: macOS Container Machines
#156In the intro it mentions automatically mapping user and home dir. So host files accessible the container. Any settings to control this?
Re: macOS Container Machines
#157Re: macOS Container Machines
#158Every time I see Apple flaunting Linux containers I can hardly consider it as anything but admitting defeat. It could easily be Darwin, if they still had the capacity.
Apple set itself up for defeat in the server and developer marketplace as soon as they decided macOS was proprietary code. Why would any serious developer use closed-source code they can't debug and modify? Especially for a production server? It's the same reason no serious developers or hackers use macOS, like part of the point of being a developer is being able to dig into the code at any layer and debug and fix th…
Apparently game, desktop and app devs aren't serious.
Re: macOS Container Machines
#159Earlier quoted context omitted.
Cygwin was fun. I'd done zero development on Windows, but about 10 years ago I had to figure out how to deploy some nightly shell scripts across a bunch of local computers in a few dozen offices, where about 80% were MacOS and the rest were Windows. I don't remember exactly how I rigged it, but basically cygwin allowed me to keep the scripts as they were and trigger them in place, with a few small modifications. I ne…
The biggest issue I remember is directory seperators... windows of course using \ which bash would then interpret as an escape. Cygwin mostly papered over that from what I can recall, but it could lead to some weirdness, like sometimes you'd get C:\\path\\es\\like\\this
We should be using the baguette emoji for path separators for cross-platform compatibility.
https://old.reddit.com/r/ProgrammerHumor/comments/96ufiz/pro...