Anybody else having problems with with rootless Docker after updating to version 29.5.0?
“docker run …” or “docker compose …”:
failed to connect to the docker API at unix:///run/user/1000/docker.sock; check if the path is correct and if the daemon is running: dial unix /run/user/1000/docker.sock: connect: no such file or directory
I assume, you created the GitHub issue as well?
Seems that: adding Environment=DOCKERD_ROOTLESS_ROOTLESSKIT_DETACH_NETNS=false in .config/systemd/user/docker.service.d/override.conf fix it (when using slirp4netns).
Can someone explain it?
slirp4netns is a network driver to isolate your rootless Docker’s network from your host so you have your own network namespace for the rootless docker daemon. If you disable the network namespace entirely, there will be no problem with slirp4netns either as it will not be used.
Then, what will be used?
Nothing. You disabled network namespace isolation so no need for any tool that does network namespace solation. Note that we are talking about the Docker daemon itself, not the network inside containers.
So networks inside Docker are still managed by slirp4netns? I’m totally a newbie in docker networking.
Managed by whatever rootless Docker’s network is based on. But that has nothing to do with the network namespace of the Docker daemon.
Since this topic was about a specific issue, I recommend opening a new topic if you want to learn about rootless Docker’s network modes. I rarely use Rootless Docker, so I would nott to refresh my memory before giving a good answer, and I am not on Linux now, but that would have nothing to do with how the daemon is isolated from the rest of the system Since the whole point of rootles Docker is running the daemon as a non-root user which has limitied privileges, de network has to be a little different.