This is a direct consequence of bug 1575572. In particular this part:
runcmd:
- [ systemctl, start, dcos-docker-install.service ]
In 16.04 final this was not actually working. I. e. you asked for
starting this service, but it wasn't actually started. This got fixed in
bug 1575572, so that packages that you install in "packages:" or
"runcmd:" (which start services) or direct start requests like your's
from above now actually do what you asked it to.
So this is indeed a behaviour change, but I fail to see how it is a
regression and not a bug fix? I. e. can you clarify why you would expect
docker not to start despite your explicit runcmd to do so?
** Changed in: init-system-helpers (Ubuntu)
Status: New => Incomplete
** Changed in: init-system-helpers (Ubuntu Xenial)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588477
Title:
regression-update: systemd init behavior change
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1588477/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
