On 9/6/19 1:21 PM, Felicia wrote:
Package: docker.io
Version: 18.09.5+dfsg1-1
Severity: important
Dear Maintainer,
After a recent upgrade to linux-image-5.2.0-2-amd64 docker no longer starts
with the following reported by systemd:
Hi Felicia,
can you give us more logs regarding your issue? Maybe try that:
- stop docker: sudo systemctl stop docker
- watch the logs: journalctl -f
- start docker in another shell: sudo systemctl start docker
Then watch the logs, and if you can't sort it out yourself you can paste
it here, in case we can help.
FYI I don't see the problem you mention, with the same version of docker
and the kernel that you have.
$ dpkg -l | grep -E 'docker.io|linux-image-amd64'
ii docker.io 18.09.1+dfsg1-9
ii linux-image-amd64 5.2+106~bpo10+1
If I run the following from the command line:
$ sudo /usr/sbin/dockerd -H fd://
it produces the following output:
Failed to load listeners: no sockets found via socket activation: make
sure the service was started by systemd
Indeed, you should start docker using `systemctl start docker`.
According to other forum posts I've read, one recommendation was to
change fd:// to unix://.
Hmm I don't know about that, but I don't think it's a good idea. Things
should work out of the box.
In order to override the systemd ExecStart command I did:
$ sudo systemctl edit docker.service
and put the following lines in the file:
[Service]
ExecStart=
ExecStart=/usr/sbin/dockerd -H unix:// $DOCKER_OPTS
Please be sure to revert this change to the original value
"ExecStart=/usr/sbin/dockerd -H fd:// $DOCKER_OPTS", there is really no
need to modify this line.
Best regards,
Arnaud
