slonopotamus

You mean, Earthly has macOS arm64 runners? I am failing to find any info on its website.

Okay, let's call them "labeled code snapshots")

Haha, what a mess)

Yeah, I undestand the situation with #8789.

It's not me, it's containerd "native" snapshotter. It turns to be efficient on macOS thanks to `clonefile` syscall.

> Technical limitations aren’t excuses for a bad design.

Tomorrow Apple might decide it is safe to chroot with SIP enabled (I actually do not understand why they restrict it, chroot is a tool to increase security). Does that suddenly convert bad design into a good design? But this is exactly the same design.

One might develop a game that by some kind of a miracle releases for macOS too. So they way to run CI tests on macOS. Or they might target iOS. And use macOS build machines to produce builds. The world is not only about web, you know?

OrbStack is about Linux containers. What we're talking about in this topic is the only software in the world for macOS containers.

> My preferred course of action in such situations is not specify a version at all.

This doesn't work because, well, I do make releases and they need some numbers)

FUSE is only used for bind mounts. If you write to a directory that belongs to container, you get the raw speed of host OS.

I believe that could be optimized in the future. At least, by splitting amd64/arm64 code.

> macOS doesn't provide a stable system call API

I'm really wondering, do you have any links about macOS syscall stability over versions?

SIP won't save you from wrong file permissions.

And SIP doesn't defend you from editing files in /bin. They are guarded by the fact that root filesystem is mounted read-only.