Your message dated Wed, 8 Jan 2020 03:06:09 +0800
with message-id
<CAFyCLW_p=a0nua_y+ow24znfn_kc+ylmyzavxnnnt5ffjdf...@mail.gmail.com>
and subject line Closing old bugs when docker.io depends extra containerd
package
has caused the Debian Bug report #855922,
regarding containerd: 0.2.3 ds1-1 breaks docker 1.11 - unable to start
containerd
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 ow...@bugs.debian.org
immediately.)
--
855922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: containerd
Version: 0.2.3~git20161117.78.03e5862~ds1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After upgrading containerd from 0.2.1~ds1-3 to
0.2.3~git20161117.78.03e5862~ds1-1, docker service does not start correctly
(hangs).
Unable to start docker service
% systemctl start docker.service:
Feb 23 10:06:25 pcricardo-debian systemd[1]: Starting Docker Application
Container Engine...
Feb 23 10:06:25 pcricardo-debian docker[5328]:
time="2017-02-23T10:06:25.851495304-03:00" level=info msg="New containerd
process, pid: 5334\n"
Feb 23 10:06:25 pcricardo-debian docker[5328]:
time="2017-02-23T10:06:25.863535053-03:00" level=warning msg="containerd:
89e9a962159c157d04b08174cd57b8774133ff3f78eaec3b188861c4f7fca441:init shim
died, killing associated process"
Feb 23 10:06:25 pcricardo-debian docker[5328]:
time="2017-02-23T10:06:25.926085808-03:00" level=error msg="containerd: notify
OOM events" error="open /proc/4868/cgroup: no such file or directory"
Feb 23 10:06:25 pcricardo-debian docker[5328]:
time="2017-02-23T10:06:25.92673198-03:00" level=fatal msg="bad listen address
format /var/run/docker/libcontainerd/docker-containerd.sock, expected
proto://address"
Feb 23 10:06:31 pcricardo-debian docker[5328]:
time="2017-02-23T10:06:31.853710940-03:00" level=info msg="New containerd
process, pid: 5359\n"
Feb 23 10:06:31 pcricardo-debian docker[5328]:
time="2017-02-23T10:06:31.866868174-03:00" level=warning msg="containerd:
89e9a962159c157d04b08174cd57b8774133ff3f78eaec3b188861c4f7fca441:init (pid
4868) does not exist"
Feb 23 10:06:31 pcricardo-debian docker[5328]:
time="2017-02-23T10:06:31.867110238-03:00" level=error msg="containerd: notify
OOM events" error="open /proc/4868/cgroup: no such file or directory"
Feb 23 10:06:31 pcricardo-debian docker[5328]:
time="2017-02-23T10:06:31.867155272-03:00" level=fatal msg="bad listen address
format /var/run/docker/libcontainerd/docker-containerd.sock, expected
proto://address"
* What outcome did you expect instead?
Docker service to be running
Downgrading containerd to 0.2.1-ds1-3 fixes the issue
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-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 containerd depends on:
ii libc6 2.24-9
ii runc 0.1.1+dfsg1-2
containerd recommends no packages.
containerd suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: containerd
Source-Version: 1.3.2~ds1-2
Sorry for disturbing after a long while. Just doing housekeep on bugs
of containerd package.
The bug shouldn't exist anymore. The docker.io package have shipped
both /usr/bin/docker and /usr/bin/docker-containerd together for a
while. And they should work without problem.
--
Shengjing Zhu
--- End Message ---
