Your message dated Mon, 02 Jul 2018 05:49:32 +0000
with message-id <[email protected]>
and subject line Bug#786724: fixed in docker.io 18.03.1+dfsg1-5
has caused the Debian Bug report #786724,
regarding seems to forget about containers that were running when it was 
upgraded
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
786724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786724
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Source: docker.io
Source-Version: 18.03.1+dfsg1-5

We believe that the bug you reported is fixed in the latest version of
docker.io, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov <[email protected]> (supplier of updated docker.io package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 02 Jul 2018 14:56:46 +1000
Source: docker.io
Binary: docker.io vim-syntax-docker golang-github-docker-docker-dev 
golang-docker-dev docker-doc
Architecture: source all amd64
Version: 18.03.1+dfsg1-5
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov <[email protected]>
Changed-By: Dmitry Smirnov <[email protected]>
Description:
 docker-doc - Linux container runtime -- documentation
 docker.io  - Linux container runtime
 golang-docker-dev - Transitional package for golang-github-docker-docker-dev
 golang-github-docker-docker-dev - reusable Go packages included with Docker
 vim-syntax-docker - Docker container engine - Vim highlighting syntax files
Closes: 786724 902258
Changes:
 docker.io (18.03.1+dfsg1-5) unstable; urgency=medium
 .
   * New upstream patch to prevent needless calls to `pass` (Closes: #902258).
   * Do not automatically restart daemon on upgrade (Closes: #786724).
   * Recommends += "needrestart".
 .
     "needrestart" prompts to restart "docker" daemon on upgrade. This way
     running containers won't be killed on upgrade until user choses to
     restart Docker.
     Not restarting Docker on upgrade may break CLI when it disagrees with
     running daemon regarding API version.
Checksums-Sha1:
 590a7193bd8d5ef7d2c08b134a5688d741907d19 8578 docker.io_18.03.1+dfsg1-5.dsc
 a557389578456cfa914324c5ef5f8190d6c4bdfe 43744 
docker.io_18.03.1+dfsg1-5.debian.tar.xz
 e291c1a711e905e5e0f55cee8b9fd85f216eb65c 967456 
docker-doc_18.03.1+dfsg1-5_all.deb
 4acdf0d0c64f4fbc86d3702616a520761031d573 4063468 
docker.io-dbgsym_18.03.1+dfsg1-5_amd64.deb
 6a9973eb12bc165b20758cb570e8d787a5d4c7c7 25884 
docker.io_18.03.1+dfsg1-5_amd64.buildinfo
 4f0e4926c90fc6a90e041356391e7a98802c24f5 35997260 
docker.io_18.03.1+dfsg1-5_amd64.deb
 435b0ffc641d3f61bcdb18ab31f7aea658d12192 18700 
golang-docker-dev_18.03.1+dfsg1-5_all.deb
 3b6fce55d0bbec76d3c180c7b5b1b2399227c556 517576 
golang-github-docker-docker-dev_18.03.1+dfsg1-5_all.deb
 caeca09e403582b2ed68d7f57cb657684000e514 19892 
vim-syntax-docker_18.03.1+dfsg1-5_all.deb
Checksums-Sha256:
 c0024790df8cf2a08e710637c1813b808b77e01b6e094679215637bebb6c23da 8578 
docker.io_18.03.1+dfsg1-5.dsc
 0c35ef456cf126ccb8a88235a02b11c6e929903aa7f3f32fa804cc1f13ea09ae 43744 
docker.io_18.03.1+dfsg1-5.debian.tar.xz
 d571f1635622636b229fa9687ecdbdc9620bca9a3b4edcd731883eeee23c476e 967456 
docker-doc_18.03.1+dfsg1-5_all.deb
 a1175239b6b6c14285a7d3f586430ed652cbaea6afb7b14c58d52edcd6fb37f9 4063468 
docker.io-dbgsym_18.03.1+dfsg1-5_amd64.deb
 841d9fadaa7764bcfe6fcae15d5f983af03c256acfff4a45f5f88d5a8413e450 25884 
docker.io_18.03.1+dfsg1-5_amd64.buildinfo
 44ab02935796c54a99694850cd55e5db973e5c09cd2dd3a9c65de6a3305c7ff1 35997260 
docker.io_18.03.1+dfsg1-5_amd64.deb
 221caf73d3703e5bc27c622e4545b25fe79eda9478770a331334e2f7ada4a67c 18700 
golang-docker-dev_18.03.1+dfsg1-5_all.deb
 a720d618209ce2aabd002c331e33cf9d63ab8478b2a75d79b7bb5540a0bb7958 517576 
golang-github-docker-docker-dev_18.03.1+dfsg1-5_all.deb
 0926e731870b2a7d474ab13a684b77d8373caa25cd5c9acc94adf93cbacf2a35 19892 
vim-syntax-docker_18.03.1+dfsg1-5_all.deb
Files:
 7c7765f71986e8848d05d27f79a70965 8578 admin optional 
docker.io_18.03.1+dfsg1-5.dsc
 3d8b9e399bf39a25f2b798f2ace021b5 43744 admin optional 
docker.io_18.03.1+dfsg1-5.debian.tar.xz
 cdbbac2acff004e8b584ea7eb2432c07 967456 doc optional 
docker-doc_18.03.1+dfsg1-5_all.deb
 e0a579b1ac442435a98d3ccf7657696f 4063468 debug optional 
docker.io-dbgsym_18.03.1+dfsg1-5_amd64.deb
 2832b2e082490ca1b0177381af4a2db0 25884 admin optional 
docker.io_18.03.1+dfsg1-5_amd64.buildinfo
 fd8734122b148095b0a8fcc1843e5735 35997260 admin optional 
docker.io_18.03.1+dfsg1-5_amd64.deb
 795369902d8b4f26eb6e35eccd2861f3 18700 oldlibs optional 
golang-docker-dev_18.03.1+dfsg1-5_all.deb
 039b7569596a1316c8008fa861483ea2 517576 admin optional 
golang-github-docker-docker-dev_18.03.1+dfsg1-5_all.deb
 06b2234a479681293a3429dc1917b11c 19892 admin optional 
vim-syntax-docker_18.03.1+dfsg1-5_all.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAls5tcYACgkQUra72VOW
jRscfhAAh/c1l3Gwp3pTGPIjnNZyvREc0Q0XFtt6mkW84+wOseZLBvO1RNw5t0vU
0QuhVsKS7Nd8jyVJtnhEcFJHnmK/kqML1DQVTRCD5FX9EQLCu1dMC1nm8YTEtYOR
ThMNcGneLXFaIWciB9kCy21XEA4GpgF1sTx7HYQMfIK2ZkvNa8GdNnblrsc5FcYl
0rqtH81iL3lSrk0+ff1yRNJovuTHDmk5aESj6sCQGU2s8N89b+ncTbTvMRo6+kgA
PEv9BYpHo4/GSWOSENyo3uympJE4fm+WZdvqg0wAo9k/BR6ntaEHVH7BWVCvtW3P
tGZhASAJHjR56zEEKgYwsl58Oy4KyPPey3ha/i2PPEg34Nm/8RRYETa7OMYyUhZj
PNmiBUqeDDFBVVlFK9xBt45xoPMoAfsiiasHYN1Gq57ineNSAjinUu20jpPsvVHV
GCBA0ku6HpMM3V9Ndd+ARwkVGey0cikK5dwNgnNhhrBp1khVlr6XvNMjw/RMaZru
v9/ibJ2f6Gil0RCTVnB0U+dD2Wm4zpBpiSKbW6UOagBIeNZB20C9v9STgkiFZGFY
LPC8jdnuJRyQclQkr2RfirREEDKf31Va3zakdzDnMqrcIegIiwyRKlo2VZ+092zU
L28vomlm9dNOjLD/M7kyftonhCi+k/D0UUwFhpjUH3OVxrfboVQ=
=lwVw
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to