Is it safe to symlink docker.sock in MacOS ?

[paolomainardi]

Hi everyone, I have some workloads that are hardwired to /var/run/docker.sock, which is now owned by Docker Desktop. Is it safe to replace it dynamically when switching to Lima? Are there any other best practices I might be missing?

[jandubois]

It is "safe" to replace it with your symlink, but Docker Desktop may switch it back to itself if you start it again, I don't know.

Best practice would be to use a docker context, or the DOCKER_HOST environment variable, but if your workloads don't support that, then you have to do what you have to do...

[paolomainardi]

I guess I can just use the docker-rootful template to have the /var/run/docker.sock available:

lima/templates/docker-rootful.yaml

Line 63 in 86a7a5a

- guestSocket: "/var/run/docker.sock"

If i understood right, still doubt about the need of the symlink on my host. Basically I want to run Traefik, which needs /var/run/docker.sock.

[jandubois]

You are mixing up host and guest sockets. Even docker-rootful forwards the socket to a user filename on the host, and not to /var/run/docker.sock.

Where are you running traefik, inside the guest or on the host?

[paolomainardi]

You are mixing up host and guest sockets. Even docker-rootful forwards the socket to a user filename on the host, and not to /var/run/docker.sock.

Where are you running traefik, inside the guest or on the host?

I am running it as a docker container, it just needs access to docker.sock I guess with rootfull will be available in the Lima VM.

[paolomainardi]

it works with rootful.