Does Orbstack expose /run/containerd/containerd.sock inside containers like Docker Desktop does?

[kwakubiney]

On Docker Desktop for macOS, I can run the following and see that /run/containerd/containerd.sock is correctly mapped from the Docker VM into my container:

docker run -it --rm \
  -v /run/containerd/containerd.sock:/run/containerd/containerd.sock \
  alpine sh -c "ls -l /run/containerd/containerd.sock"

This works as expected on Docker Desktop.

When I try the same on Orbstack, the socket doesn’t seem to be present or mountable.

Does Orbstack expose /run/containerd/containerd.sock to containers?

If not, is there an alternative way to access containerd or equivalent low-level runtime sockets from within a container on Orbstack?

[kwakubiney]

@slinorb

[slinorb]

The containerd sock is at /run/docker/containerd/containerd.sock

[kwakubiney]

Exposed on MacOS? @slinorb, can't find it.

biney@Kwakus-MacBook-Pro ~ % file /run/docker/containerd/containerd.sock
/run/docker/containerd/containerd.sock: cannot open `/run/docker/containerd/containerd.sock' (No such file or directory)

[slinorb]

It is only available inside the Docker VM and not on the MacOS host. You can check with:

docker run -it --rm \
  -v /run/docker/containerd/containerd.sock:/run/containerd/containerd.sock \
  alpine sh -c "ls -l /run/containerd/containerd.sock"

[kwakubiney]

Interesting. I know Docker Desktop exposes it on the MacOS filesystem. Any reason why orb doesn't? Also, is this documented anywhere? @slinorb