Docker Clock Drift Update The Clock

Currently I have changed the run script in every docker to include the following lines of code.

See this QA with an answer from one of the Docker core developers.

The comment to the answer makes it clear that the clock drift does not occur as the docker and host use the same clock.

On operating systems other than linux and Windows 10 with linux subsystem, the docker machine (the host) is actually a virtual machine.

When the docker host is not the same machine as the one youre running the docker commands on, you may see time skew, and things like mounting volumes wont work as you might expect.

This also happens when you set up a remote docker machine, e.g.

Docker uses the same clock as the host and the docker cannot change it.

It means that doing an ntpdate inside the docker does not work.

If a clock drift occurs, it will happen on the dockers host machine which is where clock drift needs fixing.

Technically, docker is still in sync with its host which is the VM.

Executing date inside the container showed me same time as that on the host.

I exited from the shell and stopped the container using docker stop.

Then accessed its shell again using nsenter and found that time was now set to Singapore time zone.

Docker Clock Drift Update The Clock

To update the clock on the virtual machine without restarting run.

However, the time started drifting again and I had to run the command again.

It seems that after you restart the host the setting is unticked.

If you know where you are based (UK for me) then look at tianons answer here.

Provide details and share your research But avoid Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

Not the answer youre looking for Browse other questions tagged docker ntp or ask your own question.

Docker For Mac Clock Drift