Description of problem: Keep getting these messages in the journal after the recent update of docker. May 11 12:50:59 monster dockerd[1454]: time="2017-05-11T12:50:59.043936021+02:00" level=error msg="l ibcontainerd: failed to receive event from containerd: rpc error: code = 13 desc = transport is clos ing" May 11 12:50:59 monster dockerd[1454]: time="2017-05-11T12:50:59.044606087+02:00" level=info msg="li bcontainerd: new containerd process, pid: 17215" pid keeps incrementing and has kept on going after a reboot. $ rpm -qa --last | grep docker docker-zsh-completion-17.03.1-2.mga6.x86_64 Thu 11 May 2017 12:05:21 PM CEST docker-17.03.1-2.mga6.x86_64 Thu 11 May 2017 12:05:19 PM CEST docker-containerd-0.2.3-1.mga6.x86_64 Wed 03 May 2017 07:17:10 PM CEST
Assignee: bugsquad => bruno
Here is the log when I restarted docker just now. May 11 13:48:13 monster systemd[1]: Stopping Docker Application Container Engine... May 11 13:48:13 monster dockerd[1454]: time="2017-05-11T13:48:13.131018546+02:00" level=info msg="Processing signal 'terminated'" May 11 13:48:13 monster dockerd[1454]: time="2017-05-11T13:48:13.13152281+02:00" level=info msg="stopping containerd after receiving terminated" May 11 13:48:13 monster lxqt-panel[10607]: "/org/freedesktop/UDisks2/block_devices/loop0" lost interfaces: ("org.freedesktop.UDisks2.Filesystem") May 11 13:48:13 monster systemd[1]: Stopped Docker Application Container Engine. May 11 13:48:13 monster systemd[1]: Starting Docker Application Container Engine... May 11 13:48:13 monster dockerd[6647]: time="2017-05-11T13:48:13.291933039+02:00" level=warning msg="[!] DON'T BIND ON ANY IP ADDRESS WITHOUT setting -tlsverify IF YOU DON'T KNOW WHAT YOU'RE DOING [!]" May 11 13:48:13 monster dockerd[6647]: time="2017-05-11T13:48:13.292811740+02:00" level=info msg="libcontainerd: new containerd process, pid: 6655" May 11 13:48:14 monster lxqt-panel[10607]: "/org/freedesktop/UDisks2/block_devices/loop0" has new interfaces: ("org.freedesktop.UDisks2.Filesystem") May 11 13:48:14 monster dockerd[6647]: time="2017-05-11T13:48:14.338880539+02:00" level=warning msg="devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--stora ge-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section." May 11 13:48:14 monster lxqt-panel[10607]: "/org/freedesktop/UDisks2/block_devices/dm_2d3" has new interfaces: ("org.freedesktop.UDisks2.Block", "org.freedesktop.UDisks2.Filesystem") May 11 13:48:14 monster dockerd[6647]: time="2017-05-11T13:48:14.358819494+02:00" level=warning msg="devmapper: Base device already exists and has filesystem xfs on it. User specified filesystem will be ignored." May 11 13:48:14 monster lxqt-panel[10607]: "/org/freedesktop/UDisks2/block_devices/dm_2d3" lost interfaces: ("org.freedesktop.UDisks2.Filesystem", "org.freedesktop.UDisks2.Block") May 11 13:48:14 monster dockerd[6647]: time="2017-05-11T13:48:14.377370542+02:00" level=info msg="[graphdriver] using prior storage driver: devicemapper" May 11 13:48:14 monster dockerd[6647]: time="2017-05-11T13:48:14.406352030+02:00" level=info msg="Graph migration to content-addressability took 0.00 seconds" May 11 13:48:14 monster dockerd[6647]: time="2017-05-11T13:48:14.406535082+02:00" level=warning msg="Your kernel does not support cgroup memory limit" May 11 13:48:14 monster dockerd[6647]: time="2017-05-11T13:48:14.406563425+02:00" level=warning msg="Your kernel does not support cgroup rt period" May 11 13:48:14 monster dockerd[6647]: time="2017-05-11T13:48:14.406573562+02:00" level=warning msg="Your kernel does not support cgroup rt runtime" May 11 13:48:14 monster dockerd[6647]: time="2017-05-11T13:48:14.406649209+02:00" level=warning msg="mountpoint for pids not found" May 11 13:48:14 monster dockerd[6647]: time="2017-05-11T13:48:14.406829372+02:00" level=info msg="Loading containers: start." May 11 13:48:14 monster dockerd[6647]: time="2017-05-11T13:48:14.499708672+02:00" level=info msg="Firewalld running: false" May 11 13:48:14 monster dockerd[6647]: time="2017-05-11T13:48:14.700329151+02:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
Do you mean that after a reboot you don't have the msgs anymore for libcontainerd ? Meanwhile I have also asked for an update of docker-containerd so that may help as well. I'm running these versions on mga5 and don't see these issues and can still use my containers (I also have opencontainers-runc 1.0.0rc2)
(In reply to Bruno Cornec from comment #2) > Do you mean that after a reboot you don't have the msgs anymore for > libcontainerd ? > > Meanwhile I have also asked for an update of docker-containerd so that may > help as well. > > I'm running these versions on mga5 and don't see these issues and can still > use my containers (I also have opencontainers-runc 1.0.0rc2) Good morning. I still see these messages after a reboot, every reboot. Don't see these messages on MGA5, only MGA6. May 12 07:02:28 monster dockerd[2807]: time="2017-05-12T07:02:28.024864878+02:00" level=error msg="libcontainerd: failed to receive event from containerd: rpc error: code = 13 desc = transport is closing" May 12 07:02:28 monster dockerd[2807]: time="2017-05-12T07:02:28.026212044+02:00" level=info msg="libcontainerd: new containerd process, pid: 20570"
Latest update of docker-containerd has solved this issue.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED