On Fri, Aug 20, 2021 at 12:40 PM Forest <fores...@sonic.net> wrote: > > On Fri, 20 Aug 2021 12:09:34 +0800, Shengjing Zhu wrote: > > >This one looks almost same: > > > >https://github.com/opencontainers/runc/issues/3124 > > Hm... The conditions in that issue are different (my /proc is not mounted > with a hidepid option) but yes, the docker error message looks similar. > > >Could you try command like: > > > > busctl --user --no-pager status > > $ busctl --user --no-pager status > Failed to connect to bus: No such file or directory > > When I run it again with strace, I see this system call failing: > > connect(3, {sa_family=AF_UNIX, sun_path="/run/user/[UID]/bus"}, 21) = -1 > ENOENT (No such file or directory) > > The /run/user/[UID]/ directory does exist, both for the current user and > other users, but they do not contain a file named "bus". Perhaps because > this is a headless server with no desktop sessions at all? > > >Also as it's likely upstream issue, could you try Docker Inc's rootless > >binaries? > > I'm afraid I cannot. The policy for this machine is only to run binaries > from debian or built locally. > > However, if runc assumes the presence of /run/user/$uid/bus, that does seem > likely to be a problem, does it not?
Yes. The default mode, which is using systemd to setup cgroup, requires dbus. So you need to install dbus-user-session, which will provide /run/user/$uid/bus. Or you can use cgroupfs mode, which is mentioned in your first mail, as a workaround. -- Shengjing Zhu
