Public bug reported:
Upgrading containerd (through for example unattended upgrades) causes
the docker daemon service to be stopped but not started again.
This behavior is observed on Bionic.
The /lib/systemd/system/docker.service file contains:
BindsTo=containerd.service
This stops the docker service when the containerd service is stopped during
upgrade.
There is however no mechanism for starting the docker service again when
containerd is started.
Expected behavior would be for the docker service to start once the
containerd package has been upgraded and the containerd service has
resumed.
** Affects: docker.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906675
Title:
docker service is not started again by containterd upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906675/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
