VM / wrong date time #69
Comments
Can you open a PR? This way we'll know you're the author of the fix :) |
How do I apply this update to my boot2docker install? |
so long as you're using the |
I followed the installation instructions from docker.io here just this week. So, I should have the latest if this was there in January. Yet all the time keeps saying it's two days in the past. |
Ok, I figured out my problem when I sleep my mac then wake it up the next morning the boot2docker clock is not updating. When I bring down boot2docker then restart it works fine. |
This is not fixed. |
+1 It's still an issue. I've done a "boot2docker up" today and realized that date is "Tue Dec 9 17:59:11 UTC 2014". But in reality it's 10th December 2014, 10:14AM. |
Hi @erikprice, I can confirm that #661 does not fix this for me. Current time on OS X 23 Jan, 9:08 AM. In the container 23 Jan, 6:22 AM. Running with release 1.4.1. The workaround, as provided by Eric Silverberg, is to run the following command periodically from OS X:
|
Same here @aral. In the meantime I've been using this convenience wrapper: https://github.com/beechnut/boot2docker-ntp |
+1 to @aral, having the same issue and need to run
|
Same issue here, when I sleep my mac and wake it up the next morning the b2d clock does not update. |
This lets us continue in the face of clock skew, specifically on boot2docker: boot2docker/boot2docker#69
Host System is OSX:
OSX (Host): Fr 10 Jan 2014 04:42:26 CET
VM (Tiny Core Linux): Fri Jan 10 04:41:13 UTC 2014
to fix this you need to set this FLAG for virtual box:
--rtcuseutc on // This option lets the real-time clock (RTC) operate in UTC time
The text was updated successfully, but these errors were encountered: