Live data from Hacker News

macOS Container Machines

github.com

221–230 of 457 posts

Re: macOS Container Machines

#221
post #180

I belong to a rare breed of very opportunistic hobby-developers that like to use MacOS but also like to use linux machines or BSDs (rpi etc) sometimes. I can create docker-images with docker compose, or use something like colima, which this seems to be close to (that should have some advantages over docker, although my hope of circumventing W^X page protection did not pan out). I was perplexed that the repository doe…

https://github.com/apple/container/blob/main/docs/technical-... read documentation mr. rare breed

Like, this doesn’t answer when to use this vs Docker. Any reference there?

Re: macOS Container Machines

#222

I belong to a rare breed of very opportunistic hobby-developers that like to use MacOS but also like to use linux machines or BSDs (rpi etc) sometimes. I can create docker-images with docker compose, or use something like colima, which this seems to be close to (that should have some advantages over docker, although my hope of circumventing W^X page protection did not pan out). I was perplexed that the repository doe…

Why try to circumvent W^X page protection? Some sort of self-modifying program without extra pointer indirections?

Bad legacy apps like Xilinx ISE

Re: macOS Container Machines

#223
post #211
post #146

Earlier quoted context omitted.

For server side, which I believe is the context here, Linux and open source are king. Even Microsoft gave up on Windows and just runs Linux most things except niche cases. Heck, even SQL Server which is expensive piece of machinery got ported to Linux and that's the default target now in their docs. With that said, one can't deny Apple's success on the b2c side of things so it feels wrong to call their strategy a fai…

Except the cloud isn't open source, the ones that matter to developers that is. Which is why so many projects get burned with their license choices.

I don't see how this comment is relevant to parent's point. Sure, cloud is proprietary. But it is Linux for the vast majority.

Re: macOS Container Machines

#224
Just to clarify, this requires Mac OS 26 Tahoe for "container" doesn't it? So those of us holding out on Sequoia who can't stand the broken glass UI or what's called and the other undesired features need to stick to Docker desktop.

Re: macOS Container Machines

#225

It was unclear to me, is this a native replacement for docker? I like docker (on mac) but its quite the resource hog. I usually run like a db, redis, maybe something like rabbitmq/zeromq and have a app that uses these services (makefile/docker-compose). I would love to switch if this in fact is a lightweight replacement.

On the one hand yes, on the other hand there are already multiple lighter alternatives to docker on mac.

Re: macOS Container Machines

#226
post #26

OrbStack works really well for me. I wonder how it’s compared to this performance wise

(OrbStack dev here.) Instead of Virtualization.framework, we have a custom Rust virtualization stack with custom devices and protocols for things like filesystem sharing. It's a highly optimized vertically integrated stack specifically for running our Linux machines and containers. Our biggest perf/resource gain is dynamic memory, which reduces memory usage a lot by releasing unused memory back to macOS. Nothing else…

I changed over to Orbstack just for local builds and it is one of those apps that makes owning a Mac that much better.

This post reminded me to buy a license, just done it, worth it for the time saved.

Re: macOS Container Machines

#227
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.

Re: macOS Container Machines

#230
post #223
post #211

Earlier quoted context omitted.

Except the cloud isn't open source, the ones that matter to developers that is. Which is why so many projects get burned with their license choices.

I don't see how this comment is relevant to parent's point. Sure, cloud is proprietary. But it is Linux for the vast majority.

Which is an Pyrrhic victory, when Linus and other founders are long gone, most of this generation actually, what will subsist are proprietary forks, just like what happened with UNIX System V.
Post reply on HN