** 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 result
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: #187051
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: containerd (Ubuntu Groovy)
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/1870514
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: containerd (Ubuntu Focal)
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/1870514
Ti
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: containerd (Ubuntu Bionic)
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/1870514
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: containerd (Ubuntu Xenial)
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/1870514
T
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/1870514
Title:
** Also affects: containerd (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/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daemon
To
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 mentio
** 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/1870514
Title:
update containerd:a
As a workaround I opted for using a systemd unit file to create a loose
dependency between containerd and dockerd.
Here's how:
As root:
Make the override directory (permission 755)
mkdir /etc/systemd/system/containerd.service.d/
Create the override file in the above directory (permissions 644)
Getting about 30 other people commenting on the thread above reporting
the same issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daemon
Confirmed on 20.04 LTS.
https://www.reddit.com/r/docker/comments/k4jiyp/woke_up_to_my_docker_daemon_being_stopped_no_logs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containe
** Also affects: containerd (Ubuntu Hirsute)
Importance: Critical
Status: In Progress
** Also affects: containerd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: containerd (Ubuntu Groovy)
Status: New => In Progress
** Changed in: containerd (Ubuntu Gr
** Also affects: containerd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: containerd (Ubuntu)
Importance: Undecided => Critical
** Changed in: containerd (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: containerd (Ubuntu Bionic)
Importance: U
@Tianon, yes we're tracking the upstream changes but are not finding
them sufficient to address the issue. We're finding we need more than
just that change to BindsTo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
We have the same problem docker daemon was stopped on two EC2 instances
and never started again due to network interface being unavailable. As
everyone previously mentioned starting docker again fixes the issue,
best here is to disable updates it seems like.
--
You received this bug notification
Aha, this sounds like it's probably the same root cause that led to
https://github.com/docker/docker-ce-packaging/pull/508.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update contai
If you are currently affected:
sudo systemctl restart docker
It looks like the packaging will stop docker when containerd is stopped, but
does not start it on start and that's dropped folks into this situation. We're
working out a fix for that.
--
You received this bug notification becau
> A workaround for this seems to be to use the docker snap package.
Use caution here. Snap tends to upgrade/restart things on its own
schedule, so you might run into the same issue.
I use Apt's pinning feature to pin the Docker version on production
hosts:
```
/etc/apt/preferences.d# cat docker.
** Tags removed: regression-proposed
** Tags added: regression-security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daemon
To manage no
What does rls-ff-incoming mean? Is this something that can be fixed everywhere?
I'm pretty sure it's something that happens to mysql also:
https://askubuntu.com/q/1037285
A workaround for this seems to be to use the docker snap package. snapd seems
to keep stuff running.. at least when there isn
I can confirm this aswell for 18.04, happened this morning...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daemon
To manage notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: containerd (Ubuntu Xenial)
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/1870514
T
Confirmed on Ubuntu 20.04 LTS (GNU/Linux 5.4.0-1015-aws x86_64) with
containerd 1.3.3-0ubuntu2.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.3.3-0 stops do
** Also affects: containerd (Ubuntu Xenial)
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/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daem
After unattended-updates upgraded containerd our docker services were no
longer accessible as the docker daemon had stopped. This happened with
the update to 1.3.3-0ubuntu1~18.04.3 on Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
We have seen this on a bionic (18.04) and xenial (16.04) hosts. Does
this definitely not impact focal as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: containerd (Ubuntu Bionic)
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/1870514
T
I'm adding the rls-ff-incoming tag because the issue seem to be showing
up on every containerd update.
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
up
This also took Docker down on 18.04 with the update for USN-4653-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daemon
To manage notific
** Also affects: containerd (Ubuntu Bionic)
Importance: Undecided
Status: New
** No longer affects: containerd (Ubuntu Focal)
** Also affects: containerd (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: containerd (Ubuntu Focal)
--
You received this bu
** Also affects: containerd (Ubuntu Focal)
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/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daemo
Is there an option to publish back the 1.3.3-0ubuntu1~18.04.1 as it is
affecting a whole new deployment in a cloud?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd
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/1870514
Title:
Duplicate of https://bugs.launchpad.net/ubuntu/+source/unattended-
upgrades/+bug/1870876?comments=all
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.3.3-0 sto
** Package changed: ubuntu => containerd (Ubuntu)
** Tags added: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daemon
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
containerd:amd64 1.3.3-0ubuntu1~18.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daemon
To manage notifications about this bug go to
39 matches
Mail list logo
