On Thursday, 28 June 2018 4:11:54 PM AEST Tommi Vainikainen wrote:
> I just noticed when upgraded from 18.03.1+dfsg1-3 to 18.03.1+dfsg1-4
> that my containers were lost.
>
> If the upstream does not support upgrading docker version with
> containers kept running, I'd expect to have some warning or
Hi,
I just noticed when upgraded from 18.03.1+dfsg1-3 to 18.03.1+dfsg1-4
that my containers were lost.
If the upstream does not support upgrading docker version with
containers kept running, I'd expect to have some warning or some form
of documentation of the expected behavior here. Current silen
This is a design flaw and upstream gave up on the idea of restarting
containers on upgrade.
Docker's upgrade tip from 17.12.1 release notes states is clearly:
"You must stop all containers and plugins BEFORE upgrading"
https://github.com/docker/docker-ce/releases/tag/v17.12.1-ce
If that'
Occurs to me that I might have had docker running in a screen session to
get debug messages for the intermittent bug where docker dies of a
signal. I forget if I did, but that might have prevented a clean
shutdown on the upgrade?
I rebooted the host, and /var/lib/docker still had a lot of images i
Package: docker.io
Version: 1.6.2~dfsg1-1
Severity: normal
root@elephant:/usr/local/propellor#joeyconfig>docker start
kiteshellbox.elephant.kitenet.net.propellor
Error response from daemon: Cannot start container
kiteshellbox.elephant.kitenet.net.propellor: [8] System error: Unit
docker-8b0ea86
5 matches
Mail list logo
