I'm re-opening this. As per the previous comments, chrony indeed doesn't
work inside a container because it fails to set the time of the local
system, it crashes, and fails to start.
However, chrony should be able to run just fine inside a container even
if it cannot set the time of the local system.
This requires the '-x' option to be sent to the daemon in a container:
-x
This option disables the control of the system clock. chronyd will
not make any adjustments of the clock, but it will still track its
offset and frequency relative to the estimated true time, and be
able to operate as an NTP server. This allows chronyd to run
without the capability to adjust or set the system clock (e.g. in
some containers).
** Changed in: chrony (Ubuntu)
Status: Invalid => New
--
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
