Closed jkleiser closed 6 years ago
fundamentally, its a problem with virtualbox's virtual clock drifting, and we've tried a number of things to help, and none have been quite enough.
its possible that the vbox extensions which have been added to the next release may help.
@tianon ?
As I mentioned https://github.com/boot2docker/boot2docker/issues/544#issuecomment-58550866, this certainly could be solved very nicely by the guest additions, but those won't actually work until we can figure out a 64bit userspace or get the 32bit Guest Additions binaries working in TCL with our 64bit kernel (which I tried to do for a while and couldn't ever get working nicely).
Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).
I have not yet figured out how to get the right date/time when running the container. Is this a problem specific to Mac OSX (running this boot2docker), or is it a general Docker problem?