Our devices don’t always have internet on first power up, the reason being the upstream router takes a few minutes to boot up.
This seems to cause a conflict with the latest setting of chronyc which attempt to sync "aggressively with NTP servers for the first few minutes the device is on, but then back off to every ~4 hours.
This causes nasty SSL issues and other problems usually caused by bad time.
We’ve been bale to manually run chronyc makestep to work around this, but this can’t be done from the containers (we think?) which makes it not really an option for production.
Any ideas on how we could fix this? Is there a way to force clock sync through the supervisor api?