Yep, that would be socket activation; I'd recommend explicitly enabling "docker.service" so it starts on boot as expected. 👍
-- 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
