Comment 2 for bug 1867036

Hello Cryolithe and thanks for filing this bug report. In order to understand if what you observe is actually a bug or the expected behavior of chrony we need to know two things:

1. What is the exact version of the package you have installed?
2. Are you running Focal on bare metal, in a virtual machine, or in a container?

If you are running it in a (unprivileged) container and you have installed the latest version of the chrony package (currently 3.5-5ubuntu1), then you should see these warnings:

chronyd-starter.sh[1813]: Warning: Missing cap_sys_time, syncing the system clock will fail
chronyd-starter.sh[1813]: Warning: Running in a container, likely impossible and unintended to sync system clock
chronyd-starter.sh[1813]: Adding -x as fallback disabling control of the system clock, see /usr/share/doc/chrony/README.container to override this behavior

and chrony should start but only serve time, without setting the system clock. This is expected.

I'm setting the status of this bug report to Incomplete for the moment. Please change it back to New after commenting back, and we'll look at it again. Thanks!