Closed tilfischer closed 9 months ago
Thanks for reporting. Was it working before? Was something changed on tumbleweed recently?
Adding some path (/var/run
?) to --copy-up
helps?
https://github.com/moby/moby/blob/591c98cdbee73d36fe27abdb4456f8d70b8e549d/contrib/dockerd-rootless.sh#L107
You may need DOCKERD_ROOTLESS_ROOTLESSKIT_SLIRP4NETNS_SANDBOX=false
too
https://github.com/moby/moby/blob/591c98cdbee73d36fe27abdb4456f8d70b8e549d/contrib/dockerd-rootless.sh#L15C2-L15C2
Thank for your reply!
I added --copy-up=/var/run
to the line mentioned and uninstalled and installed rootless docker. However, this did not help.
What I have found out so far, is that netconfig was changed about a year ago, so that it does now use /run/netconfig instead of /var/run/netconfig.
Copying /var/run/netconfig/resolv.conf (or /run/netconfig/resolv.conf) to /etc or adding a symlink there for /run/netconfig/resolv.conf to /etc/resolv.conf works fine. However, with a symlink to /var/run/netconfig/resol.conf, no traffic can leave the namespace of the rootless docker.
Hence, that seems not be an issue for slirp4netns and I will close this issue.
Dear all,
recently, I faced a strange issue with rootless docker on openSUSE Tumbleweed, which prevented any pulling of images. Basically, no traffic seems to be leaving the rootlesskit's namespace. Pulling an docker images always gives an i/o timeout:
After quiet some digging and and with the help of two users at the docker forum and openSUSE forum, the issue seems to be connected to slirp4netns:
Following the slirp4netns documentation:
However, in openSUSE the resolve.conf is generated in /var/run/netconfig/ from what is given in /etc/sysconfig/network/config and the first is symlinked to /etc/resolve.conf. Removing the simlinked /etc/resolve.conf solved the issue, but should not survive any restart of the sever:
Best