I just ran into this problem. Rebooting the machine fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836022
Title:
Cannot start containers after docker.io update
To manage notifications
if need disable unattended-upgrade, add APT::Periodic::Unattended-
Upgrade "0"; in /etc/apt/apt.conf.d/10periodic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836022
Title:
Cannot start
The issue was encounter on several machines today also.
A reboot of the system allowed to restart the containers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836022
Title:
Cannot start
** Tags added: bionic xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836022
Title:
Cannot start containers after docker.io update
To manage notifications about this bug go to:
Further information:
Doing things like docker stop will hang and won't actually stop the running
container (but won't spit out an error message or exit with a non-zero return
code). docker kill fails to change the state of the system in a similar way.
In my case restarting the docker daemon
I've also seen this on multiple machines since yesterday and just like
the reporter the machines are Xenial and Bionic:
>From /var/log/apt.history.log on a Xenial machine:
Commandline: /usr/bin/unattended-upgrade
Install: containerd:amd64 (1.2.6-0ubuntu1~16.04.3, automatic)
Upgrade: apport:amd64
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/1836022
Title:
