blocks|key|5443084|text|如果您在运行boot2docker的OSX上，请参阅此问题：https://github.com/boot2docker/boot2docker/issues/290|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5443085|时间同步成为一个问题，因为当您的操作系统处于休眠状态时，boot2docker主机会出现时间漂移。无法通过使用-v+/etc/localtime:/etc/localtime:ro运行容器来解决与停靠容器的时间同步问题|style|CODE|5443086|相反，现在，您必须在OSX上定期运行以下代码：|5443087|/usr/local/bin/boot2docker+ssh+sudo+ntpclient+-s+-h+pool.ntp.org|code-block|syntax|javascript|5443088|面向用户的更新|BOLD|5443089|如果你正在运行Kitematic，它现在是在OSX中启动和运行Docker的建议机制，你将不得不定期运行这个命令：|5443090|docker-machine+ssh+default+'sudo+ntpclient+-s+-h+pool.ntp.org'|5443091|或者，对于旧版本的docker|5443092|docker-machine+ssh+dev+'sudo+ntpclient+-s+-h+pool.ntp.org'|5443093|为用于OSX的新本机Docker用户提供的更新|5443094|新的Docker+Beta取消了VirtualBox和Docker+Machine。docker的最新版本(目前为1.12.1-beta25+(版本:+11807))似乎具有检测时间中断并进行相应调整的能力。因此，这不应该再是一个issue...hooray!！|5443095|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/boot2docker/boot2docker/issues/290|1|https://kitematic.com/^0|U|1H|0|0|1J|Z|0|0|0|5|2|0|0|1L|7|9|1|0|0|0|F|0|0|0|6|L|2|0|0|3N|0^^$0|@$1|2|3|4|5|6|7|1D|8|@]|9|@$A|1E|B|1F|1|1G]]|C|$]]|$1|D|3|E|5|6|7|1H|8|@$A|1I|B|1J|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|1K|8|@]|9|@]|C|$]]|$1|J|3|K|5|L|7|1L|8|@]|9|@]|C|$M|N]]|$1|O|3|P|5|6|7|1M|8|@$A|1N|B|1O|F|Q]]|9|@]|C|$]]|$1|R|3|S|5|6|7|1P|8|@$A|1Q|B|1R|F|Q]]|9|@$A|1S|B|1T|1|1U]]|C|$]]|$1|T|3|U|5|L|7|1V|8|@]|9|@]|C|$M|N]]|$1|V|3|W|5|6|7|1W|8|@$A|1X|B|1Y|F|Q]]|9|@]|C|$]]|$1|X|3|Y|5|L|7|1Z|8|@]|9|@]|C|$M|N]]|$1|Z|3|10|5|6|7|20|8|@$A|21|B|22|F|Q]|$A|23|B|24|F|Q]]|9|@]|C|$]]|$1|11|3|12|5|6|7|25|8|@$A|26|B|27|F|Q]]|9|@]|C|$]]|$1|13|3|-4|5|6|7|28|8|@]|9|@]|C|$]]]|14|$15|$5|16|17|18|C|$19|1A]]|1B|$5|16|17|18|C|$19|1C]]]]

If you are on OSX running boot2docker, see this issue: <a href="https://github.com/boot2docker/boot2docker/issues/290">https://github.com/boot2docker/boot2docker/issues/290</a>

Time synch becomes an issue because the boot2docker host has its time drift while your OS is asleep. Time synch with your docker container cannot be resolved by running your container with <code>-v /etc/localtime:/etc/localtime:ro</code>

Instead, for now, you have to periodically run this on OSX: 

<pre><code>/usr/local/bin/boot2docker ssh sudo ntpclient -s -h pool.ntp.org
</code></pre>

Update for users of Kitematic

If you are running <a href="https://kitematic.com/">Kitematic</a>, which is now the suggested mechanism for getting up and running on Docker in OSX, you will have to periodically run this command:

<pre><code>docker-machine ssh default 'sudo ntpclient -s -h pool.ntp.org'
</code></pre>

Or, for older versions of docker

<pre><code>docker-machine ssh dev 'sudo ntpclient -s -h pool.ntp.org'
</code></pre>

Update for users of new native Docker for OSX

The new Docker Beta does away with VirtualBox and Docker Machine. The latest builds of docker (currently, 1.12.1-beta25 (build: 11807)) seem to have the ability to detect when there has been a time discontinuity and adjust accordingly. Thus, this should no longer be an issue...hooray!!

blocks|key|1578550|text|https://github.com/sameersbn/docker-gitlab/issues/77|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1578551|参见sameersbn的答案。|1578552|option+1:+-v+/etc/localtime:/etc/localtime:ro
option+2:+-e+"TZ=Asia/Shanghai"|code-block|syntax|javascript|1578553|entityMap|0|LINK|mutability|MUTABLE|url^0|0|1G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|W|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|4]]]]

<a href="https://github.com/sameersbn/docker-gitlab/issues/77">https://github.com/sameersbn/docker-gitlab/issues/77</a>

See sameersbn's answer.

<pre><code>option 1: -v /etc/localtime:/etc/localtime:ro
option 2: -e "TZ=Asia/Shanghai"
</code></pre>

blocks|key|1914045|text|最简单的解决方案似乎是使用-v+/etc/localtime:/etc/localtime:ro选项运行容器。因此：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1914046|#run+without+tz+info:
docker+run+--rm+-t+-i+ubuntu+date
Wed+Apr++2+18:40:07+UTC+2014
#+run+with+tz+info:
docker+run+--rm+-t+-i+-v+/etc/localtime:/etc/localtime:ro+ubuntu+date
Wed+Apr++2+11:40:29+PDT+2014|code-block|syntax|javascript|1914047|entityMap^0|D|Z|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

The simplest solution appears to be to run your container with the <code>-v /etc/localtime:/etc/localtime:ro</code> option. Thus:

<pre><code>#run without tz info:
docker run --rm -t -i ubuntu date
Wed Apr 2 18:40:07 UTC 2014
# run with tz info:
docker run --rm -t -i -v /etc/localtime:/etc/localtime:ro ubuntu date
Wed Apr 2 11:40:29 PDT 2014
</code></pre>

blocks|key|1574562|text|在Docker+for+Mac+OS+X+Beta上，我体验到了基于高山Linux的VM的重大漂移。在Alpine+Linux+FAQ中，您可以使用以下命令同步VM的时钟。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1574563|ntpd+-d+-q+-n+-p+pool.ntp.org|code-block|syntax|javascript|1574564|但是，访问VM上的终端是另一个问题，如果使用screen命令就可以做到这一点。|1574565|screen+~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty|1574566|该路径是一个符号链接，它在我的系统上指向/dev/ttys003。|style|CODE|1574567|一旦进入，请注意moby+login只是没有密码的root。完成后，按CTRL-A、D将断开与屏幕会话的连接。|1574568|备注：这曾经在Docker+for+Mac+Trouble+Shooting上记录过，但现在似乎已经被删除了。我很幸运地在Dockercon+2016上看到了它。Docker似乎试图将VM完全从体验中抽象出来，这就解释了为什么它不再有文档记录。|BOLD|1574569|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.alpinelinux.org/wiki/Alpine_Linux:FAQ#Using_a_cron_job_to_keep_the_time_in_sync|1|https://docs.docker.com/docker-for-mac/troubleshoot/#issues^0|1F|G|0|0|0|0|0|K|C|0|8|A|P|4|0|0|3|7|V|1|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]]|C|$]]|$1|D|3|E|5|F|7|19|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|1A|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|1B|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|1C|8|@$A|1D|B|1E|O|P]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1F|8|@$A|1G|B|1H|O|P]|$A|1I|B|1J|O|P]]|9|@]|C|$]]|$1|S|3|T|5|6|7|1K|8|@$A|1L|B|1M|O|U]]|9|@$A|1N|B|1O|1|1P]]|C|$]]|$1|V|3|-4|5|6|7|1Q|8|@]|9|@]|C|$]]]|W|$X|$5|Y|Z|10|C|$11|12]]|13|$5|Y|Z|10|C|$11|14]]]]

On Docker for Mac OS X Beta, I experienced significant drift on the VM, which is based on Alpine Linux. From <a href="https://wiki.alpinelinux.org/wiki/Alpine_Linux:FAQ#Using_a_cron_job_to_keep_the_time_in_sync">Alpine Linux FAQ</a> you can synchronize the VM's clock with the following command.

<pre><code>ntpd -d -q -n -p pool.ntp.org
</code></pre>

However, getting access to a terminal on the VM is another question, which can be done if you use the screen command. 

<pre><code>screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty
</code></pre>

That path is a symlink, which on my system points at <code>/dev/ttys003</code>.

Once you get in, note that the <code>moby login</code> is simply <code>root</code> with no password. After you have finished, CTRL-A, D will disconnect from the screen session.

NOTE: This used to be documented on <a href="https://docs.docker.com/docker-for-mac/troubleshoot/#issues">Docker for Mac Trouble Shooting</a> but that seems to have been taken down. I was lucky enough to be shown it while at Dockercon 2016. It seems Docker is trying to abstract the VM completely out of the experience, which explains why it's no longer documented.

blocks|key|5443174|text|docker上osx时间漂移的当前解决方案(2018年4月)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5443175|我的mac是在一个NTP服务器上，但是这个固定的时钟会随着容器的变化而变化：|5443176|来自https://docs.docker.com/docker-for-mac/troubleshoot/#known-issues：|offset|length|5443177|如果您的系统无法访问NTP服务器，则在休眠后，Docker+for+Mac看到的时间可能与主机严重不同步。此外，在使用过程中，时间可能会慢慢地不同步。要在休眠后手动重置时间，请运行以下命令：|5443178|docker+run+--rm+--privileged+alpine+hwclock+-s|code-block|syntax|javascript|5443179|或者，要解决这两个问题，您可以将本地时钟添加为主机的低优先级(高层)回退NTP时间源。为此，请编辑主机的/etc/ntp-restrict.conf以添加：|5443180|server+127.127.1.1++++++++++++++#+LCL,+local+clock
fudge++127.127.1.1+stratum+12+++#+increase+stratum|5443181|然后使用以下命令重新启动NTP服务：|5443182|sudo+launchctl+unload+/System/Library/LaunchDaemons/org.ntp.ntpd.plist
sudo+launchctl+load+/System/Library/LaunchDaemons/org.ntp.ntpd.plist|5443183|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/docker-for-mac/troubleshoot/#known-issues^0|0|0|2|1T|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@$F|17|G|18|1|19]]|A|$]]|$1|H|3|I|5|6|7|1A|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1B|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1D|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1E|8|@]|9|@]|A|$]]|$1|U|3|V|5|L|7|1F|8|@]|9|@]|A|$M|N]]|$1|W|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

The current solution for osx time drift on docker (April 2018):

I do have my mac on an NTP server, but this fixed clock drift with containers:

From <a href="https://docs.docker.com/docker-for-mac/troubleshoot/#known-issues" rel="nofollow noreferrer">https://docs.docker.com/docker-for-mac/troubleshoot/#known-issues</a> :

If your system does not have access to an NTP server, then after a hibernate the time seen by Docker for Mac may be considerably out of sync with the host. Furthermore, the time may slowly drift out of sync during use. To manually reset the time after hibernation, run:

<pre><code>docker run --rm --privileged alpine hwclock -s
</code></pre>

Or, to resolve both issues, you can add the local clock as a low-priority (high stratum) fallback NTP time source for the host. To do this, edit the host’s /etc/ntp-restrict.conf to add:

<pre><code>server 127.127.1.1 # LCL, local clock
fudge 127.127.1.1 stratum 12 # increase stratum
</code></pre>

Then restart the NTP service with:

<pre><code>sudo launchctl unload /System/Library/LaunchDaemons/org.ntp.ntpd.plist
sudo launchctl load /System/Library/LaunchDaemons/org.ntp.ntpd.plist
</code></pre>

blocks|key|1914219|text|docker-compose用法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1914220|向volumes属性添加/etc/localtime:/etc/localtime:ro。|offset|length|style|CODE|1914221|查看此link以演示一个示例。|1914222|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/51942316/3702377^0|0|1|7|C|W|0|3|4|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]|$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

<h1>docker-compose usage:</h1>

Add <code>/etc/localtime:/etc/localtime:ro</code> to the <code>volumes</code> attribute.

Look at this <a href="https://stackoverflow.com/a/51942316/3702377">link</a> to demonstrate an example.

blocks|key|1914241|text|如果你更喜欢TZ解决方案，那么你可能会惊讶地发现，尽管你要求自己的时区，但却显示了UTC时间(目前是11:09+CDT)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1914242|$+docker+run+--rm+-it+-e+"TZ=America/Chicago"+ubuntu+date
Mon+Oct+26+16:09:04+America+2020|code-block|syntax|javascript|1914243|在实验中，您似乎需要POSIX+TZ格式：|1914244|$+docker+run+--rm+-it+-e+"TZ=CST6CDT"+ubuntu+date
Mon+Oct+26+11:09:17+CDT+2020|1914245|entityMap^0|6|2|0|0|G|2|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

If you prefer the <code>TZ</code> solution then you may be surprised to see UTC time displayed despite your request for your own timezone (it's currently 11:09 CDT):
<pre><code>$ docker run --rm -it -e &quot;TZ=America/Chicago&quot; ubuntu date
Mon Oct 26 16:09:04 America 2020
</code></pre>
Experimentally, it seems you need the POSIX <code>TZ</code> format:
<pre><code>$ docker run --rm -it -e &quot;TZ=CST6CDT&quot; ubuntu date
Mon Oct 26 11:09:17 CDT 2020
</code></pre>

Do I need a NTP server inside a docker container to periodically sync the time or will the container re-sync time with its host machine? The docker container time zone is correctly set.

Will a docker container auto sync time with its host machine?

5位重磅专家聚焦 AI 时代开发者核心成长需求，带你深入解锁全栈进化、人机协作关键路径！点击报名到场：<a href="https://cloud.tencent.com/developer/salon/salon-2403/signup" target="_blank">https://cloud.tencent.com/developer/salon/salon-2403/signup</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/487c82639d2338df3ef66dfb1450601a.png"/>

腾讯技术创作特训营「年度论坛」正在报名中！

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我是否需要docker容器内的NTP服务器来定期同步时间，或者容器是否会与其主机重新同步时间？docker容器时区设置正确。

问docker容器是否会自动与其主机同步时间？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问docker容器是否会自动与其主机同步时间？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问docker容器是否会自动与其主机同步时间？
EN