docker service is not started again by containterd upgrade
Bug #1906675 reported by
Vinjar Hillestad
This bug report is a duplicate of:
Bug #1906364: [SRU] unattended-upgrade still restarts blacklisted daemons.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| docker.io (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
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/
BindsTo=
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.
To post a comment you must log in.
