Thanks for the report, and congratulations on figuring out what was going on! I can see why the behaviour is as described on a very shallow level: xenial postrm masks both the service and socket units but the bionic postinst just unmasks the socket. Deeper than that, I really don't know. The way the service file is installed is different on xenial, it's installed via the .install file and maybe that makes dh_systemd do something different. Perhaps the pragmatic fix is to just explicitly insert "deb-systemd-helper unmask docker.service >/dev/null || true" into the postinst in bionic+?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844894 Title: docker doesn’t start in bionic (Unit docker.service is masked), if previously installed+removed in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1844894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
