Thanks for taking a look, Tianon. You're right that Docker appears to be
behaving normally... running journalctl -b I see that the system did in
fact reboot causing the Docker shutdown, and that it came back online at
19:29:45 with multiuser system target being reached at 19:30:04.
So my issue is with why it took systemd so long after bootup to start
dockerd, not with Docker itself... apologies for not checking that out
first. I'm guessing that there is something in the CLI that told systemd
to start it when I ran docker ps?
** Changed in: docker.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808266
Title:
Docker daemon drops all bound ports, recovers them after long docker
ps
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1808266/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
