Viewing profile — slonopotamus

If you want to follow my upstream attempts, subscribe to https://github.com/moby/buildkit/pull/4059 https://github.com/moby/moby/pull/46558

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, chroo…

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 prod…

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.

This is a failed attempt to upstream part of containerd changes: https://github.com/containerd/containerd/pull/8789 Other part of containerd changes waits for gods-know-what: https…

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

Original author here. I wanted to clearly indicate early-prealpha-unstable-not-for-production-yet state of this software. Using "1.0.0" and even "1.0.0-alpha" would give false expe…

No. For the same reason you cannot run Windows containers on Linux. You need a working macOS kernel.

> But most it’s still very niche. I'd say that the whole containerization topic is niche > Is there a way to make a separate partition of MacOS and have one copy with SIP and one w…

> Who would use that and for what? I believe this project can be useful for CI and testing scenarios. > On MacOS desktop software distribution is largely a solved problem since age…

> Also not sure if it can be dynamically set by a parent process for a child? Yes, it can. See sandbox-exec tool. And I actually plan to use it: https://github.com/macOScontainers/…

I didn't want to use "jail" term because it is mostly unheard of outside of FreeBSD. Container definition is very stretched nowadays. Look at Windows HostProcesses in Kubernetes [1…

What exactly attack vectors you think are possible against macOS without SIP but not possible against Linux?

> this doesn't give me anything extra to what using docker would do on macos You're missing the point. This project DOES use docker.

You can just mount it readonly.

> And that’s a good thing? That's a technical limitation.