On Mon, Feb 02, 2026 at 12:02:34PM +0100, Miroslav Lichvar wrote: > On Sat, Jan 31, 2026 at 07:23:12PM +0100, Joachim Tingvold wrote: > > If not, what should the chrony-config look like on the client (hosts) and > > server (ntp1+2)? Would it be possible to have equal config on all hosts > > (regardless if ntp1+2 is running as LXC container on said host or not), to > > ease config-deployment of chrony on the hosts? Preferably a setup where > > only ntp1+2 has access to the external NTP-servers (i.e. hosts will not). > > My suggestion would be to run the server together with the client on > the host. If that's not possible, run the server in a virtual machine, > which has its own clock.
To clarify that a bit, I don't recommend synchronizing a client to a server using the same clock as that creates a feedback loop. That applies also to other servers that might be synchronized to this server (the loop can form over multiple servers). A client synchronizing to other time sources and a separate server instance running on the same host using the -x option is ok. There is no loop. Whether the client and/or server run in a container, that doesn't really matter. -- Miroslav Lichvar -- To unsubscribe email [email protected] with "unsubscribe" in the subject. For help email [email protected] with "help" in the subject. Trouble? Email [email protected].
