Public bug reported:
I had raised this situation in the past but I think back in the day we
didn't look into this topic in the right direction (we looked into the
configuration files inside /etc/chrony instead of investigating how the
systemd unit would be implemented). WSL is a kind of container where
CAP_SYS_TIME is available and it's beneficial to have chrony.service
enabled. It's possible to have the WSL time out of sync after the
Windows host is resumed from suspension. chrony.service allows fixing
it.
Since #2111535 we completely disabled that unit for containers, and
since questing we have chrony.service replacing systemd-
timesyncd.service, thus we lost the ability to recover the system time
on WSL.
My proposal is to replace the `ConditionVirtualization=!container` line
in the `chrony.service` unit with the following:
```
ConditionVirtualization=|!container
ConditionVirtualization=|wsl
```
That still disables the unit on containers by default, except on WSL.
As Debian also ships WSL images, I consider beneficial to have this patch
upstreamed to Salsa, thus I'm keen to open a small merge proposal there if I
receive a positive feedback here.
** Affects: chrony (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122337
Title:
chrony should not run inside containers **but WSL**
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2122337/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
