[Group.of.nepali.translators] [Bug 1870514] Re: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon
This bug was fixed in the package docker.io - 19.03.13-0ubuntu3.1
---
docker.io (19.03.13-0ubuntu3.1) groovy; 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: #1870514)
* d/rules: Fix docker.io to not restart its service during package
upgrades, to prevent service downtime from automatic updates via
unattended-upgrade.
(LP: #1906364)
-- Bryce Harrington Fri, 04 Dec 2020 23:02:49
+
** Changed in: docker.io (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** Changed in: containerd (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1870514
Title:
[SRU] update containerd:amd64 1.3.3-0 stops docker daemon
Status in containerd package in Ubuntu:
Fix Released
Status in docker.io package in Ubuntu:
Fix Released
Status in containerd source package in Xenial:
Fix Released
Status in docker.io source package in Xenial:
Fix Released
Status in containerd source package in Bionic:
Fix Released
Status in docker.io source package in Bionic:
Fix Released
Status in containerd source package in Focal:
Fix Released
Status in docker.io source package in Focal:
Fix Released
Status in containerd source package in Groovy:
Fix Released
Status in docker.io source package in Groovy:
Fix Released
Status in containerd source package in Hirsute:
Fix Released
Status in docker.io source package in Hirsute:
Fix Released
Bug description:
[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 in unexpected and widespread
service outages for docker.
[Test Case]
$ sudo apt install docker.io
$ sudo systemctl start docker
$ systemctl status docker | grep Active
Active: active (running) since[...]
$ systemctl status containerd | grep Active
Active: active (running) since[...]
$ docker pull ubuntu/redis:latest
$ docker run -e REDIS_PASSWORD=1234 --network host \
--name test-redis -d ubuntu/redis:latest
$ telnet localhost 6379
$ docker container logs test-redis
$ sudo apt install --reinstall containerd
$ systemctl status containerd | grep Active
Active: active (running) since
$ systemctl status docker | grep Active
Active: inactive (dead) since [...]; 8s ago
$ docker container logs test-redis
[Where Problems Could Occur]
The challenge with this issue is addressing all important corner
cases, and as such the biggest risk is that we miss a corner case and
fail to keep the two services running when they should. Areas to
watch will be failures during start/stop/restart/upgrade type
operations. Issues during runtime are unlikely to relate to this
change.
[Original Report]
hello we have had in several vms, the problem that after updating to "
containerd:amd64 1.3.3" the docker daemon is stopped and so are all
running containers
the vms run with ubuntu 18.04.1/18.04.2
journal log during the update:
```
-- Logs begin at Tue 2020-01-14 09:58:27 CET, end at Fri 2020-04-03 11:30:39
CEST. --
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.648358396Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.660781933Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line=\"\""
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s3 works fine"}
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s8 works fine"}
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.650166885Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.663239678Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890
[Group.of.nepali.translators] [Bug 1870514] Re: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon
This bug was fixed in the package docker.io - 18.09.7-0ubuntu1~16.04.7
---
docker.io (18.09.7-0ubuntu1~16.04.7) xenial; 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: #1870514)
* d/rules: Fix docker.io to not restart its service during package
upgrades, to prevent service downtime from automatic updates via
unattended-upgrade.
(LP: #1906364)
-- Bryce Harrington Fri, 04 Dec 2020 23:02:49
+
** Changed in: containerd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1870514
Title:
[SRU] update containerd:amd64 1.3.3-0 stops docker daemon
Status in containerd package in Ubuntu:
Fix Released
Status in docker.io package in Ubuntu:
Fix Released
Status in containerd source package in Xenial:
Fix Released
Status in docker.io source package in Xenial:
Fix Released
Status in containerd source package in Bionic:
Fix Released
Status in docker.io source package in Bionic:
Fix Released
Status in containerd source package in Focal:
Fix Released
Status in docker.io source package in Focal:
Fix Released
Status in containerd source package in Groovy:
Fix Released
Status in docker.io source package in Groovy:
Fix Released
Status in containerd source package in Hirsute:
Fix Released
Status in docker.io source package in Hirsute:
Fix Released
Bug description:
[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 in unexpected and widespread
service outages for docker.
[Test Case]
$ sudo apt install docker.io
$ sudo systemctl start docker
$ systemctl status docker | grep Active
Active: active (running) since[...]
$ systemctl status containerd | grep Active
Active: active (running) since[...]
$ docker pull ubuntu/redis:latest
$ docker run -e REDIS_PASSWORD=1234 --network host \
--name test-redis -d ubuntu/redis:latest
$ telnet localhost 6379
$ docker container logs test-redis
$ sudo apt install --reinstall containerd
$ systemctl status containerd | grep Active
Active: active (running) since
$ systemctl status docker | grep Active
Active: inactive (dead) since [...]; 8s ago
$ docker container logs test-redis
[Where Problems Could Occur]
The challenge with this issue is addressing all important corner
cases, and as such the biggest risk is that we miss a corner case and
fail to keep the two services running when they should. Areas to
watch will be failures during start/stop/restart/upgrade type
operations. Issues during runtime are unlikely to relate to this
change.
[Original Report]
hello we have had in several vms, the problem that after updating to "
containerd:amd64 1.3.3" the docker daemon is stopped and so are all
running containers
the vms run with ubuntu 18.04.1/18.04.2
journal log during the update:
```
-- Logs begin at Tue 2020-01-14 09:58:27 CET, end at Fri 2020-04-03 11:30:39
CEST. --
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.648358396Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.660781933Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line=\"\""
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s3 works fine"}
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s8 works fine"}
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.650166885Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.663239678Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line=\"
[Group.of.nepali.translators] [Bug 1870514] Re: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon
This bug was fixed in the package containerd - 1.3.7-0ubuntu3.2
---
containerd (1.3.7-0ubuntu3.2) groovy; urgency=medium
* d/control: add a Breaks for docker.io lower than 19.03.13-0ubuntu3.1
(LP: #1870514). The previous versions stop the docker daemon when a
containerd update is performed, this Breaks statement will make sure we
have a newer version which has the appropriate fix.
-- Lucas Kanashiro Fri, 11 Dec 2020 09:19:07
-0300
** Changed in: containerd (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** Changed in: docker.io (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1870514
Title:
[SRU] update containerd:amd64 1.3.3-0 stops docker daemon
Status in containerd package in Ubuntu:
Fix Released
Status in docker.io package in Ubuntu:
Fix Released
Status in containerd source package in Xenial:
Fix Released
Status in docker.io source package in Xenial:
Fix Released
Status in containerd source package in Bionic:
Fix Released
Status in docker.io source package in Bionic:
Fix Released
Status in containerd source package in Focal:
Fix Released
Status in docker.io source package in Focal:
Fix Released
Status in containerd source package in Groovy:
Fix Released
Status in docker.io source package in Groovy:
Fix Released
Status in containerd source package in Hirsute:
Fix Released
Status in docker.io source package in Hirsute:
Fix Released
Bug description:
[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 in unexpected and widespread
service outages for docker.
[Test Case]
$ sudo apt install docker.io
$ sudo systemctl start docker
$ systemctl status docker | grep Active
Active: active (running) since[...]
$ systemctl status containerd | grep Active
Active: active (running) since[...]
$ docker pull ubuntu/redis:latest
$ docker run -e REDIS_PASSWORD=1234 --network host \
--name test-redis -d ubuntu/redis:latest
$ telnet localhost 6379
$ docker container logs test-redis
$ sudo apt install --reinstall containerd
$ systemctl status containerd | grep Active
Active: active (running) since
$ systemctl status docker | grep Active
Active: inactive (dead) since [...]; 8s ago
$ docker container logs test-redis
[Where Problems Could Occur]
The challenge with this issue is addressing all important corner
cases, and as such the biggest risk is that we miss a corner case and
fail to keep the two services running when they should. Areas to
watch will be failures during start/stop/restart/upgrade type
operations. Issues during runtime are unlikely to relate to this
change.
[Original Report]
hello we have had in several vms, the problem that after updating to "
containerd:amd64 1.3.3" the docker daemon is stopped and so are all
running containers
the vms run with ubuntu 18.04.1/18.04.2
journal log during the update:
```
-- Logs begin at Tue 2020-01-14 09:58:27 CET, end at Fri 2020-04-03 11:30:39
CEST. --
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.648358396Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.660781933Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line=\"\""
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s3 works fine"}
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s8 works fine"}
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.650166885Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.663239678Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line=\"
[Group.of.nepali.translators] [Bug 1870514] Re: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon
This bug was fixed in the package containerd - 1.3.3-0ubuntu1~18.04.4
---
containerd (1.3.3-0ubuntu1~18.04.4) bionic; urgency=medium
* d/control: add a Breaks for docker.io lower than 19.03.6-0ubuntu1~18.04.3
(LP: #1870514). The previous versions stop the docker daemon when a
containerd update is performed, this Breaks statement will make sure we
have a newer version which has the appropriate fix.
-- Lucas Kanashiro Fri, 11 Dec 2020 09:19:07
-0300
** Changed in: docker.io (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1870514
Title:
[SRU] update containerd:amd64 1.3.3-0 stops docker daemon
Status in containerd package in Ubuntu:
Fix Released
Status in docker.io package in Ubuntu:
Fix Released
Status in containerd source package in Xenial:
Fix Committed
Status in docker.io source package in Xenial:
Fix Released
Status in containerd source package in Bionic:
Fix Released
Status in docker.io source package in Bionic:
Fix Released
Status in containerd source package in Focal:
Fix Released
Status in docker.io source package in Focal:
Fix Released
Status in containerd source package in Groovy:
Fix Released
Status in docker.io source package in Groovy:
Fix Committed
Status in containerd source package in Hirsute:
Fix Released
Status in docker.io source package in Hirsute:
Fix Released
Bug description:
[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 in unexpected and widespread
service outages for docker.
[Test Case]
$ sudo apt install docker.io
$ sudo systemctl start docker
$ systemctl status docker | grep Active
Active: active (running) since[...]
$ systemctl status containerd | grep Active
Active: active (running) since[...]
$ docker pull ubuntu/redis:latest
$ docker run -e REDIS_PASSWORD=1234 --network host \
--name test-redis -d ubuntu/redis:latest
$ telnet localhost 6379
$ docker container logs test-redis
$ sudo apt install --reinstall containerd
$ systemctl status containerd | grep Active
Active: active (running) since
$ systemctl status docker | grep Active
Active: inactive (dead) since [...]; 8s ago
$ docker container logs test-redis
[Where Problems Could Occur]
The challenge with this issue is addressing all important corner
cases, and as such the biggest risk is that we miss a corner case and
fail to keep the two services running when they should. Areas to
watch will be failures during start/stop/restart/upgrade type
operations. Issues during runtime are unlikely to relate to this
change.
[Original Report]
hello we have had in several vms, the problem that after updating to "
containerd:amd64 1.3.3" the docker daemon is stopped and so are all
running containers
the vms run with ubuntu 18.04.1/18.04.2
journal log during the update:
```
-- Logs begin at Tue 2020-01-14 09:58:27 CET, end at Fri 2020-04-03 11:30:39
CEST. --
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.648358396Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.660781933Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line=\"\""
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s3 works fine"}
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s8 works fine"}
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.650166885Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.663239678Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line=\"\""
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909
[Group.of.nepali.translators] [Bug 1870514] Re: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon
This bug was fixed in the package docker.io - 19.03.8-0ubuntu1.20.04.2
---
docker.io (19.03.8-0ubuntu1.20.04.2) focal; 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: #1870514)
* d/rules: Fix docker.io to not restart its service during package
upgrades, to prevent service downtime from automatic updates via
unattended-upgrade.
(LP: #1906364)
-- Bryce Harrington Fri, 04 Dec 2020 23:02:49
+
** Changed in: docker.io (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: containerd (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1870514
Title:
[SRU] update containerd:amd64 1.3.3-0 stops docker daemon
Status in containerd package in Ubuntu:
Fix Released
Status in docker.io package in Ubuntu:
Fix Released
Status in containerd source package in Xenial:
Fix Committed
Status in docker.io source package in Xenial:
Fix Released
Status in containerd source package in Bionic:
Fix Released
Status in docker.io source package in Bionic:
Fix Released
Status in containerd source package in Focal:
Fix Released
Status in docker.io source package in Focal:
Fix Released
Status in containerd source package in Groovy:
Fix Released
Status in docker.io source package in Groovy:
Fix Committed
Status in containerd source package in Hirsute:
Fix Released
Status in docker.io source package in Hirsute:
Fix Released
Bug description:
[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 in unexpected and widespread
service outages for docker.
[Test Case]
$ sudo apt install docker.io
$ sudo systemctl start docker
$ systemctl status docker | grep Active
Active: active (running) since[...]
$ systemctl status containerd | grep Active
Active: active (running) since[...]
$ docker pull ubuntu/redis:latest
$ docker run -e REDIS_PASSWORD=1234 --network host \
--name test-redis -d ubuntu/redis:latest
$ telnet localhost 6379
$ docker container logs test-redis
$ sudo apt install --reinstall containerd
$ systemctl status containerd | grep Active
Active: active (running) since
$ systemctl status docker | grep Active
Active: inactive (dead) since [...]; 8s ago
$ docker container logs test-redis
[Where Problems Could Occur]
The challenge with this issue is addressing all important corner
cases, and as such the biggest risk is that we miss a corner case and
fail to keep the two services running when they should. Areas to
watch will be failures during start/stop/restart/upgrade type
operations. Issues during runtime are unlikely to relate to this
change.
[Original Report]
hello we have had in several vms, the problem that after updating to "
containerd:amd64 1.3.3" the docker daemon is stopped and so are all
running containers
the vms run with ubuntu 18.04.1/18.04.2
journal log during the update:
```
-- Logs begin at Tue 2020-01-14 09:58:27 CET, end at Fri 2020-04-03 11:30:39
CEST. --
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.648358396Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.660781933Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line=\"\""
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s3 works fine"}
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s8 works fine"}
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.650166885Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.663239678Z caller=loki.go:55
container_id=1eefb971e84cdaa4
[Group.of.nepali.translators] [Bug 1870514] Re: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon
fixed in hirsute by 1.3.7-0ubuntu5
** Changed in: containerd (Ubuntu Hirsute)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1870514
Title:
[SRU] update containerd:amd64 1.3.3-0 stops docker daemon
Status in containerd package in Ubuntu:
Fix Released
Status in docker.io package in Ubuntu:
Fix Released
Status in containerd source package in Xenial:
Fix Committed
Status in docker.io source package in Xenial:
Fix Committed
Status in containerd source package in Bionic:
Fix Committed
Status in docker.io source package in Bionic:
Fix Committed
Status in containerd source package in Focal:
Fix Committed
Status in docker.io source package in Focal:
Fix Committed
Status in containerd source package in Groovy:
Fix Committed
Status in docker.io source package in Groovy:
Fix Committed
Status in containerd source package in Hirsute:
Fix Released
Status in docker.io source package in Hirsute:
Fix Released
Bug description:
[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 in unexpected and widespread
service outages for docker.
[Test Case]
$ sudo apt install docker.io
$ sudo systemctl start docker
$ systemctl status docker | grep Active
Active: active (running) since[...]
$ systemctl status containerd | grep Active
Active: active (running) since[...]
$ docker pull ubuntu/redis:latest
$ docker run -e REDIS_PASSWORD=1234 --network host \
--name test-redis -d ubuntu/redis:latest
$ telnet localhost 6379
$ docker container logs test-redis
$ sudo apt install --reinstall containerd
$ systemctl status containerd | grep Active
Active: active (running) since
$ systemctl status docker | grep Active
Active: inactive (dead) since [...]; 8s ago
$ docker container logs test-redis
[Where Problems Could Occur]
The challenge with this issue is addressing all important corner
cases, and as such the biggest risk is that we miss a corner case and
fail to keep the two services running when they should. Areas to
watch will be failures during start/stop/restart/upgrade type
operations. Issues during runtime are unlikely to relate to this
change.
[Original Report]
hello we have had in several vms, the problem that after updating to "
containerd:amd64 1.3.3" the docker daemon is stopped and so are all
running containers
the vms run with ubuntu 18.04.1/18.04.2
journal log during the update:
```
-- Logs begin at Tue 2020-01-14 09:58:27 CET, end at Fri 2020-04-03 11:30:39
CEST. --
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.648358396Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00"
level=info msg="level=info ts=2020-04-03T04:09:09.660781933Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line=\"\""
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s3 works fine"}
Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03
06:09:14+02:00","message":"interface enp0s8 works fine"}
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.650166885Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00"
level=info msg="level=info ts=2020-04-03T04:09:24.663239678Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line=\"\""
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Apr 03 06:09:31 server systemd[1]: Starting Daily apt upgrade and clean
activities...
Apr 03 06:09:39 server dockerd[1751]: time="2020-04-03T06:09:39+02:00"
level=info msg="level=info ts=2020-04-03T04:09:39.64981528Z caller=loki.go:55
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f
msg=\"ignoring empty line\" line="
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
Ap
