** Description changed:
+ [Impact]
+
+ Docker uses containerd under the hood. When containerd is upgraded it
+ stops and restarts its service; docker stops when containerd stops but
+ doesn’t restart. Particularly when doing unattended upgrades, an SRU
+ fix rolled out for containerd can
This bug was fixed in the package docker.io - 19.03.13-0ubuntu4
---
docker.io (19.03.13-0ubuntu4) hirsute; urgency=medium
* d/p/do_not_bind_docker_to_containerd.patch: Update docker.io to not
stop when containerd is upgraded, by using Wants= rather than BindTo=.
(LP:
Thanks @bryce for the detailed updates.
For us personally its the second time we run into a docker daemon
restart on production (including all container restarts).
The only reason why this time it got much more attention is that a bug
prevented a clean restart of the daemon, leaving containers
I'd like to give you all an update and outline our plans for this.
The Canonical server team has made analysis of this issue a top
priority. We've identified and tested out several possible theories.
Our findings suggest that the breakage involves two distinct issues, one
the BindTo= issue
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/docker.io/+git/docker.io/+merge/394913
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906364
Title:
unattended-upgrade
This sounds like another dupe of
https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906364
Title:
unattended-upgrade still restarts
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: docker.io (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906364
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: containerd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906364
Title:
Sorry but im not really on your side here and it also doesnt really
solve the problem.
I added docker.io to the blacklist because i want to take care manually
about the upgrades, it should leave in any case this package alone.
Adding here dependencies (containerd) for the packages will never
Containerd unsuccessfully restarting docker is tracked at LP: #1870514.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906364
Title:
unattended-upgrade still restarts blacklisted daemons
To manage
I'm sorry you experienced problems when unattended-upgrades applied
security fixes.
Failure to restart a service is either an issue with the package or with
the local configuration, thus I mark docker.io and containerd being
affected.
The blacklist is listing _packages_ not services and not
** Also 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/1906364
Title:
unattended-upgrade still restarts blacklisted daemons
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906364
We have at least 4 servers on which docker daemon was shutdown due to
this unattended upgrade, and was not restarted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906364
Title:
unattended-upgrade
14 matches
Mail list logo
