Note: while the wrapper approach would work (after some test and polishing), compared to the upstream -X it will have one drawback.
If future containers grow time-namespacing as a feature it will still default to not adjusting the time in containers. But as long as we don't know how time-namespaces will be implemented we can't code special cases for that (while chrony itself can try and fallback which is the -X option). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589780 Title: chrony.service doesn't start on LXD container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1589780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
