[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
*** This bug is a duplicate of bug 1870514 *** https://bugs.launchpad.net/bugs/1870514 With the latest version on groovy, I've noticed the following message on upgrade: /var/lib/dpkg/info/docker.io.postinst: 31: zfs: not found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
*** This bug is a duplicate of bug 1870514 *** https://bugs.launchpad.net/bugs/1870514 As a follow-up for the unattended-upgrades problem I've proposed a possible enhancement to protect services by holding back more packages: https://github.com/mvo5/unattended-upgrades/issues/284 ** Bug watch added: github.com/mvo5/unattended-upgrades/issues #284 https://github.com/mvo5/unattended-upgrades/issues/284 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
*** This bug is a duplicate of bug 1870514 *** https://bugs.launchpad.net/bugs/1870514 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) vi override.conf Add the following to the file [Unit] Before=docker.service Wants=docker.service Restart systemd daemon systemctl daemon-reload Check it works Stop containerd systemctl stop containerd Check dockerd has stopped systemctl status docker Start containerd systemctl start containerd Check dockerd has started systemctl status docker ++ Some links to other documentation on the subject https://www.shellhacks.com/systemd-service-file-example/ https://man7.org/linux/man-pages/man5/systemd.service.5.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
*** This bug is a duplicate of bug 1870514 *** https://bugs.launchpad.net/bugs/1870514 For the record, running "apt install --reinstall containerd" is enough to reproduce it. It seems fine after restarting it. Investigating... root@sec-bionic-amd64:~# systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled) Active: inactive (dead) since Tue 2020-12-01 16:00:41 UTC; 7min ago Docs: https://docs.docker.com Process: 4877 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=0/SUCCES Main PID: 4877 (code=exited, status=0/SUCCESS) Dec 01 15:59:29 sec-bionic-amd64 dockerd[4877]: time="2020-12-01T15:59:29.713508745Z" level=info msg="Default bridge (docker0) Dec 01 15:59:29 sec-bionic-amd64 dockerd[4877]: time="2020-12-01T15:59:29.736687490Z" level=info msg="Loading containers: done Dec 01 15:59:29 sec-bionic-amd64 dockerd[4877]: time="2020-12-01T15:59:29.757566608Z" level=info msg="Docker daemon" commit=36 Dec 01 15:59:29 sec-bionic-amd64 dockerd[4877]: time="2020-12-01T15:59:29.757781776Z" level=info msg="Daemon has completed ini Dec 01 15:59:29 sec-bionic-amd64 systemd[1]: Started Docker Application Container Engine. Dec 01 15:59:29 sec-bionic-amd64 dockerd[4877]: time="2020-12-01T15:59:29.773817892Z" level=info msg="API listen on /var/run/d Dec 01 16:00:41 sec-bionic-amd64 systemd[1]: Stopping Docker Application Container Engine... Dec 01 16:00:41 sec-bionic-amd64 dockerd[4877]: time="2020-12-01T16:00:41.297477601Z" level=info msg="Processing signal 'termi Dec 01 16:00:41 sec-bionic-amd64 dockerd[4877]: time="2020-12-01T16:00:41.297999367Z" level=info msg="Daemon shutdown complete Dec 01 16:00:41 sec-bionic-amd64 systemd[1]: Stopped Docker Application Container Engine. root@sec-bionic-amd64:~# sudo systemctl restart docker root@sec-bionic-amd64:~# sudo systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-12-01 16:07:49 UTC; 889ms ago Docs: https://docs.docker.com Main PID: 5246 (dockerd) Tasks: 8 CGroup: /system.slice/docker.service └─5246 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock Dec 01 16:07:49 sec-bionic-amd64 dockerd[5246]: time="2020-12-01T16:07:49.423538001Z" level=warning msg="Your kernel does not Dec 01 16:07:49 sec-bionic-amd64 dockerd[5246]: time="2020-12-01T16:07:49.423617408Z" level=warning msg="Your kernel does not Dec 01 16:07:49 sec-bionic-amd64 dockerd[5246]: time="2020-12-01T16:07:49.423689794Z" level=warning msg="Your kernel does not Dec 01 16:07:49 sec-bionic-amd64 dockerd[5246]: time="2020-12-01T16:07:49.423861920Z" level=info msg="Loading containers: star Dec 01 16:07:49 sec-bionic-amd64 dockerd[5246]: time="2020-12-01T16:07:49.474290225Z" level=info msg="Default bridge (docker0) Dec 01 16:07:49 sec-bionic-amd64 dockerd[5246]: time="2020-12-01T16:07:49.495593769Z" level=info msg="Loading containers: done Dec 01 16:07:49 sec-bionic-amd64 dockerd[5246]: time="2020-12-01T16:07:49.516250280Z" level=info msg="Docker daemon" commit=36 Dec 01 16:07:49 sec-bionic-amd64 dockerd[5246]: time="2020-12-01T16:07:49.516470764Z" level=info msg="Daemon has completed ini Dec 01 16:07:49 sec-bionic-amd64 systemd[1]: Started Docker Application Container Engine. Dec 01 16:07:49 sec-bionic-amd64 dockerd[5246]: time="2020-12-01T16:07:49.536722771Z" level=info msg="API listen on /var/run/d root@sec-bionic-amd64:~# root@sec-bionic-amd64:~# apt install --reinstall containerd Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-5.4.0-42-generic linux-hwe-5.4-headers-5.4.0-42 linux-image-5.4.0-42-generic linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/21.7 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 209664 files and directories currently installed.) Preparing to unpack .../containerd_1.3.3-0ubuntu1~18.04.3_amd64.deb ... Unpacking containerd (1.3.3-0ubuntu1~18.04.3) over (1.3.3-0ubuntu1~18.04.3) ... Setting up containerd (1.3.3-0ubuntu1~18.04.3) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... root@sec-bionic-amd64:~# systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled) Active: inactive (dead) since Tue 2020-12-01 16:08:01 UTC; 6s ago Docs: https://docs.docker.com Main PID: 5246 (code=exited, status=0/SUCCESS) Dec 01 16:07:49
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
*** This bug is a duplicate of bug 1870514 *** https://bugs.launchpad.net/bugs/1870514 ** This bug has been marked a duplicate of bug 1870514 update containerd:amd64 1.3.3-0 stops docker daemon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
Hello, we have same problem here on Ubuntu Bionic. Problem can be reproduced if you reinstall package 'containerd' : apt install containerd --reinstall After installation, docker is stopped: docker ps Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
I think this bug is duplicate of https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
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 Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
Maybe a workaround fix could be to restart ubuntu if dependent services had to be stopped to update something? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
Here are people who are hit by this except for mysql: https://askubuntu.com/questions/1037285/starting-daily-apt-upgrade-and-clean-activities-stopping-mysql-service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
attaching unattended-upgrades-dpkg.log ** Attachment added: "/var/log/unattended-upgrades/unattended-upgrades-dpkg.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+attachment/5346860/+files/unattended-upgrades-dpkg.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
attaching unattended-upgrades.log ** Attachment added: "/var/log/unattended-upgrades/unattended-upgrades.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+attachment/5346859/+files/unattended-upgrades.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: New Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
