You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 1, 2021. It is now read-only.
Note that the adjtime amount increases constantly. It is never actually brought back up to speed with the host system time.
If I manually run sudo ntpclient -s -h 0.boot2docker.pool.ntp.org it fixes the time momentarily but it drifts fairly quickly and VBoxService still shows the offset.
This is not the issue with the machine going to sleep. This happens on a fresh uninterrupted VM.
Update:
If I use the --timesync-set-threshold 1 it will set the time explicitly every time and that at least keeps the clock in sync but it is a terrible solution.
The text was updated successfully, but these errors were encountered:
wglambert
added
question
Usability question, not directly related to an error with Boot2Docker
Issue
and removed
question
Usability question, not directly related to an error with Boot2Docker
labels
Jul 11, 2018
The time in VirtualBox for constantly drifts on OS X. Within minutes the time is wrong.
I tried running
sudo VBoxService -f -vvv --enable-timesync --timesync-interval 1000
and this is what I get:Note that the adjtime amount increases constantly. It is never actually brought back up to speed with the host system time.
If I manually run
sudo ntpclient -s -h 0.boot2docker.pool.ntp.org
it fixes the time momentarily but it drifts fairly quickly and VBoxService still shows the offset.This is not the issue with the machine going to sleep. This happens on a fresh uninterrupted VM.
Update:
If I use the
--timesync-set-threshold 1
it will set the time explicitly every time and that at least keeps the clock in sync but it is a terrible solution.The text was updated successfully, but these errors were encountered: