I have created a container with Debian (Debian 11 template) on top of Proxmox 7.0.8. It is essential that the operating system keep the time synchronized and for this I installed chrony, but it does not start.
journalct -xe dump:
root@pamiweb:~# journalctl -xe
-- Support: https://www.debian.org/support
--
-- A start job for unit chrony.service has begun execution.
--
-- The job identifier is 1038110.
Jan 31 15:45:55 pamiweb systemd[77723]: chrony.service: Failed to set up mount namespacing: /run/systemd/unit-root/proc: Permission denied
Jan 31 15:45:55 pamiweb systemd[77723]: chrony.service: Failed at step NAMESPACE spawning /usr/sbin/chronyd: Permission denied
-- Subject: Process /usr/sbin/chronyd could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The process /usr/sbin/chronyd could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Jan 31 15:45:55 pamiweb systemd[1]: chrony.service: Control process exited, code=exited, status=226/NAMESPACE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit chrony.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 226.
Jan 31 15:45:55 pamiweb systemd[1]: chrony.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit chrony.service has entered the 'failed' state with result 'exit-code'.
Jan 31 15:45:55 pamiweb systemd[1]: Failed to start chrony, an NTP client/server.
-- Subject: A start job for unit chrony.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit chrony.service has finished with a failure.
--
-- The job identifier is 1038110 and the job result is failed.
lines 6027-6062/6062 (END)
systemctl status chrony dump:
chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2023-01-30 18:50:13 UTC; 20h ago
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
Process: 15390 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=226/NAMESPACE)
CPU: 7ms
Jan 30 18:50:13 pamiweb systemd[1]: Starting chrony, an NTP client/server...
Jan 30 18:50:13 pamiweb systemd[15390]: chrony.service: Failed to set up mount namespacing: /run/systemd/unit-root/proc: Permission denied
Jan 30 18:50:13 pamiweb systemd[15390]: chrony.service: Failed at step NAMESPACE spawning /usr/sbin/chronyd: Permission denied
Jan 30 18:50:13 pamiweb systemd[1]: chrony.service: Control process exited, code=exited, status=226/NAMESPACE
Jan 30 18:50:13 pamiweb systemd[1]: chrony.service: Failed with result 'exit-code'.
Jan 30 18:50:13 pamiweb systemd[1]: Failed to start chrony, an NTP client/server.
UPDATE:
Following @NikitaKipriyanov's recommendations I have configured chrony on the proxmox host to update the time from an external server directly. So far so good, but I don't see the container updating the time. Both the proxmox host and the container have the same time zone in /etc/timezone.
When I manually dpkg-reconfigure tzdata on the container, it instantly updates the time, but lags again.
When doing systemctl status systemd-timesyncd.service, it throws:
systemd-timesyncd.service - Network Time Synchronization
Loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Condition: start condition failed at Wed 2023-03-08 15:34:55 CST; 7s ago
ConditionVirtualization=!container was not met
Docs: man:systemd-timesyncd.service(8)
Mar 08 14:12:46 vmproxy-5 systemd[1]: Condition check resulted in Network Time Synchronization being skipped.
Mar 08 15:34:55 vmproxy-5 systemd[1]: Condition check resulted in Network Time Synchronization being skipped.
