Package: docker.io Version: 1.3.0~dfsg1-1 Severity: normal IIRC, in previous versions of docker, if a container was running when the system got rebooted, docker started the container back up on boot. This is no longer happening. Seems a problem if docker is being used to run servers.
For example:
root@clam:~>docker.io ps --all
CONTAINER ID IMAGE COMMAND CREATED
STATUS PORTS NAMES
689c8107e810 957699f2f56a "/usr/local/propello 12 days ago
Exited (-1) About a minute ago
webserver.clam.kitenet.net.propellor
root@clam:~>uptime
01:46:17 up 0 min, 1 user, load average: 0.95, 0.30, 0.10
root@clam:~>systemctl status -l docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled)
Active: active (running) since Thu 2014-10-23 01:45:44 JEST; 36s ago
Docs: http://docs.docker.com
Main PID: 515 (docker)
CGroup: /system.slice/docker.service
└─515 /usr/bin/docker -d -H fd://
Oct 23 01:45:48 clam docker[515]: 2014/10/23 01:45:48 docker daemon: 1.3.0
c78088f; execdriver: native; graphdriver:
Oct 23 01:45:48 clam docker[515]: [dbd07b0c] +job serveapi(fd://)
Oct 23 01:45:48 clam docker[515]: [info] Listening for HTTP on fd ()
Oct 23 01:45:49 clam docker[515]: [dbd07b0c] +job init_networkdriver()
Oct 23 01:45:50 clam docker[515]: [dbd07b0c] -job init_networkdriver() = OK (0)
Oct 23 01:45:51 clam docker[515]: 2014/10/23 01:45:51 WARNING: mountpoint for
memory not found
Oct 23 01:45:51 clam docker[515]: [info] Loading containers:
Oct 23 01:45:51 clam docker[515]: ....[info] : done.
Oct 23 01:45:51 clam docker[515]: [dbd07b0c] +job acceptconnections()
Oct 23 01:45:51 clam docker[515]: [dbd07b0c] -job acceptconnections() = OK (0)
Oct 23 01:46:10 clam docker[515]: [info] GET /v1.15/containers/json?all=1
Oct 23 01:46:10 clam docker[515]: [dbd07b0c] +job containers()
Oct 23 01:46:10 clam docker[515]: [dbd07b0c] -job containers() = OK (0)
--
see shy jo
signature.asc
Description: Digital signature
