Hello, Luciano Laratelli <luci...@laratel.li> writes:
> Hi, hope you are doing well. > > I’m running Guix System and am seeing that `dockerd' fails to start on boot > due to not being able to find `containerd': > > $ sudo tail /var/log/docker.log > 2022-06-12 18:25:29 time=“2022-06-12T18:25:29.969005384-04:00” level=warning > msg=“Error (Unable to complete atomic operation, key modified) deleting > object [endpoint > 062e6856b7776daf35f1d570dc7e055d3c0f3eefc0f58c5e279eba20035c8e9e > eb10082295c7a53d882e36d93a8b5eb20e980a5950c4a67fa03444274448b232], retrying….” > 2022-06-12 18:25:30 time=“2022-06-12T18:25:30.068910364-04:00” level=info > msg=“Removing stale sandbox > e35667a7ef1441bced213cf035efc9d6c71a0dce7f8941e3fbb63f5a27265bca > (91314e5594f72585f9df121ba16cc8d67c4e1fcb91fc3c7b9b0660aed1b3054a)” > 2022-06-12 18:25:30 time=“2022-06-12T18:25:30.080685302-04:00” level=warning > msg=“Error (Unable to complete atomic operation, key modified) deleting > object [endpoint > 062e6856b7776daf35f1d570dc7e055d3c0f3eefc0f58c5e279eba20035c8e9e > 825f4a6f68b1b81b24b2edc0b382deca116e72a75e6207036f24e18ba6434c81], retrying….” > 2022-06-12 18:25:30 time=“2022-06-12T18:25:30.143624227-04:00” level=info > msg=“Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. > Daemon option –bip can be used to set a preferred IP address” > 2022-06-12 18:25:31 time=“2022-06-12T18:25:31.400700443-04:00” level=info > msg=“Loading containers: done.” > 2022-06-12 18:25:31 time=“2022-06-12T18:25:31.689183684-04:00” level=info > msg=“Docker daemon” commit=v19.03.15 graphdriver(s)=overlay2 > version=19.03.15-ce > 2022-06-12 18:25:31 time=“2022-06-12T18:25:31.691171101-04:00” level=info > msg=“Daemon has completed initialization” > 2022-06-12 18:25:31 time=“2022-06-12T18:25:31.961049886-04:00” level=info > msg=“API listen on /var/run/docker.sock” > 2022-06-12 18:43:43 time=“2022-06-12T18:43:43.503118343-04:00” level=info > msg=“Starting up” > 2022-06-12 18:43:43 failed to start containerd: exec: “containerd”: > executable file not found in $PATH It seems there's a race condition between containerd and docker (the later starts before the former is done launching and it fails to see it, aborting, if I understand). We should see if we can migrate the dockerd-service-type to use the newly introduced systemd-style constructor. Thanks, Maxim
