This bug was fixed in the package chrony - 4.6.1-1ubuntu2
---------------
chrony (4.6.1-1ubuntu2) questing; urgency=medium
* d/chrony.service: Do not run inside containers by default (LP: #2111535)
Still allow running tests in containers, by installing override
configs in /etc/systemd/system/chrony.service.d/
* d/tests: Clean up after __no_system_clock_control()
* d/t/helper-functions: Do not fail if backup does not exist
* d/t/default-ubuntu-sources-behavior: Adopt to upstream container handling.
-- Lukas Märdian <[email protected]> Tue, 03 Jun 2025 10:13:08 +0200
** Changed in: chrony (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2111535
Title:
chrony should not run inside containers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2111535/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
