Hello Danny, Sorry for the delay.
Danny Milosavljevic <[email protected]> writes: > Hi Maxim, > > On Thu, 28 May 2020 09:24:58 -0400 > Maxim Cournoyer <[email protected]> wrote: > >> FWIW, I started experimenting the same on my Guix System after a recent >> guix pull & guix system reconfigure. > > Really? Back then I've fixed and replaced a lot of the modprobe stuff in > docker upstream--so now it should start up much more reliably on Guix. Really! :-/. I've reconfigured earlier and just rebooted now, and dockerd was stopped: --8<---------------cut here---------------start------------->8--- $ sudo herd status dockerd Password: Status of dockerd: It is stopped. It is enabled. Provides (dockerd). Requires (containerd dbus-system elogind file-system-/sys/fs/cgroup/blkio file-system-/sys/fs/cgroup/cpu file-system-/sys/fs/cgroup/cpuset file-system-/sys/fs/cgroup/devices file-system-/sys/fs/cgroup/memory file-system-/sys/fs/cgroup/pids networking udev). Conflicts with (). Will be respawned. --8<---------------cut here---------------end--------------->8--- > I don't know what could be up with it now. Could you please check logs > in /var/log/containerd.log and /var/log/docker.log (without > manually starting docker beforehand). Something interesting from containerd.log: --8<---------------cut here---------------start------------->8--- time="2020-05-31T22:28:15.863091224-04:00" level=info msg="starting containerd" revision=.m version= time="2020-05-31T22:28:15.883644866-04:00" level=info msg="loading plugin "io.containerd.content.v1.content"..." type=io.containerd.content.v1 time="2020-05-31T22:28:15.883714657-04:00" level=info msg="loading plugin "io.containerd.snapshotter.v1.btrfs"..." type=io.containerd.snapshotter.v1 time="2020-05-31T22:28:15.883975218-04:00" level=info msg="loading plugin "io.containerd.snapshotter.v1.aufs"..." type=io.containerd.snapshotter.v1 time="2020-05-31T22:28:15.885343166-04:00" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.aufs" error="modprobe aufs failed: "modprobe: FATAL: Module aufs not found in directory /lib/modules/5.4.43-gnu\n": exit status 1" time="2020-05-31T22:28:15.885391522-04:00" level=info msg="loading plugin "io.containerd.snapshotter.v1.native"..." type=io.containerd.snapshotter.v1 time="2020-05-31T22:28:15.885483513-04:00" level=info msg="loading plugin "io.containerd.snapshotter.v1.overlayfs"..." type=io.containerd.snapshotter.v1 time="2020-05-31T22:28:15.885632392-04:00" level=info msg="loading plugin "io.containerd.snapshotter.v1.zfs"..." type=io.containerd.snapshotter.v1 time="2020-05-31T22:28:15.885850392-04:00" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.zfs" error="path /var/lib/containerd/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter" time="2020-05-31T22:28:15.885871090-04:00" level=info msg="loading plugin "io.containerd.metadata.v1.bolt"..." type=io.containerd.metadata.v1 time="2020-05-31T22:28:15.885918881-04:00" level=warning msg="could not use snapshotter aufs in metadata plugin" error="modprobe aufs failed: "modprobe: FATAL: Module aufs not found in directory /lib/modules/5.4.43-gnu\n": exit status 1" time="2020-05-31T22:28:15.885937520-04:00" level=warning msg="could not use snapshotter zfs in metadata plugin" error="path /var/lib/containerd/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter" time="2020-05-31T22:28:15.911651119-04:00" level=info msg="loading plugin "io.containerd.differ.v1.walking"..." type=io.containerd.differ.v1 time="2020-05-31T22:28:15.911693576-04:00" level=info msg="loading plugin "io.containerd.gc.v1.scheduler"..." type=io.containerd.gc.v1 --8<---------------cut here---------------end--------------->8--- The only new lines to appear in docker.log following my last reboot are: --8<---------------cut here---------------start------------->8--- time="2020-05-31T22:28:13.579626539-04:00" level=info msg="Starting up" failed to start containerd: exec: "containerd": executable file not found in $PATH --8<---------------cut here---------------end--------------->8--- So, it seems the failure is related to kernel modules not being found where they are looked for? I think there were some changes recently in this area, but I haven't followed closely. Maxim
