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-8b0ea86c864c612cc843ee17689956add6d6877a3dadf7040069bd4a3b0a8c1a.scope already exists. FATA[0000] Error: failed to start one or more containers
root@elephant:/usr/local/propellor#joeyconfig>systemctl status
docker-8b0ea86c864c612cc843ee17689956add6d6877a3dadf7040069bd4a3b0a8c1a.scope
● docker-8b0ea86c864c612cc843ee17689956add6d6877a3dadf7040069bd4a3b0a8c1a.scope
- docker container
8b0ea86c864c612cc843ee17689956add6d6877a3dadf7040069bd4a3b0a8c1a
Loaded: loaded
Drop-In:
/run/systemd/system/docker-8b0ea86c864c612cc843ee17689956add6d6877a3dadf7040069bd4a3b0a8c1a.scope.d
└─50-BlockIOAccounting.conf, 50-CPUAccounting.conf,
50-Description.conf, 50-MemoryAccounting.conf, 50-Slice.conf
Active: active (running) since Thu 2015-03-12 20:08:22 JEST; 2 months 12
days ago
CGroup:
/system.slice/docker-8b0ea86c864c612cc843ee17689956add6d6877a3dadf7040069bd4a3b0a8c1a.scope
├─ 5916
/usr/local/propellor/docker/kiteshellbox.elephant.kitenet.net.propellor.shim/lib64/propellor
--library-path /usr/local/propellor/...
├─11560 /usr/bin/shellinaboxd -q
--background=/var/run/shellinaboxd.pid -c /var/lib/shellinabox -p 443 -u
shellinabox -g shellinabox --us...
├─11561 /usr/bin/shellinaboxd -q
--background=/var/run/shellinaboxd.pid -c /var/lib/shellinabox -p 443 -u
shellinabox -g shellinabox --us...
├─19890 bash -l
├─19892 bash -l
└─19895 id -u
docker ps doesn't show this container, which was set up before
docker was upgraded to this new release.
But, the container is actually running.
here's what docker ps --all shows:
8b0ea86c864c joeyh/debian-stable-amd64:latest
"\"/usr/local/propel 10 weeks ago Exited (-1) 2 days ago
kiteshellbox.elephant.kitenet.net.propellor
At this point I don't know how to clean up. I tried systemctl stop
to stop the procecesses, which it did, but docker start still fails
the same way.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages docker.io depends on:
ii adduser 3.113+nmu3
ii init-system-helpers 1.23
ii iptables 1.4.21-2+b1
ii libapparmor1 2.9.2-3
ii libc6 2.19-18
ii libdevmapper1.02.1 2:1.02.90-2.2
ii libsqlite3-0 3.8.10.2-1
ii perl 5.20.2-6
Versions of packages docker.io recommends:
ii aufs-tools 1:3.2+20130722-1.1
ii ca-certificates 20141019
ii cgroupfs-mount 1.2
ii git 1:2.1.4-2.1
ii xz-utils 5.1.1alpha+20120614-2+b3
Versions of packages docker.io suggests:
pn btrfs-tools <none>
ii debootstrap 1.0.70
pn lxc <none>
pn rinse <none>
-- no debconf information
--
see shy jo
signature.asc
Description: Digital signature
