Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade causes the daemon to loose time periodically #1617

Closed
buchs opened this issue May 15, 2017 · 4 comments
Closed

Upgrade causes the daemon to loose time periodically #1617

buchs opened this issue May 15, 2017 · 4 comments

Comments

@buchs
Copy link

buchs commented May 15, 2017

Expected behavior

The containers I run should track local system time.

Actual behavior

They containers time becomes skewed wrt local system time.

Information

I regularly run containers which perform operations on AWS. If the time for transactions is ahead of AWS time, they can fail. I found that once the daemon is running for something > 15 minutes, the time can be off and commands to AWS fail. If I stop and restart the daemon, this problem is immediately resolved. This ill behavior seemed to start with a recent update of Docker for Mac.

  • Full output of the diagnostics from "Diagnose & Feedback" in the menu

Docker for Mac: version: 17.03.1-ce-mac12 (d1db12684)
macOS: version 10.12.3 (build: 16D32)
logs: /tmp/24349EED-8987-48B0-87C7-F6D14028C0ED/20170515-090951.tar.gz
[OK] vmnetd
[OK] dns
[OK] driver.amd64-linux
[OK] virtualization VT-X
[OK] app
[OK] moby
[OK] system
[OK] moby-syslog
[OK] db
[OK] env
[OK] virtualization kern.hv_support
[OK] slirp
[OK] osxfs
[OK] moby-console
[OK] logs
[OK] docker-cli
[OK] menubar
[OK] disk

  • A reproducible case if this is a bug, Dockerfiles FTW
  • Page URL if this is a docs issue or the name of a man page

Steps to reproduce the behavior

  1. have the daemon running for some time > 15 minutes
  2. run a container and observe the time is skewed
@buchs
Copy link
Author

buchs commented May 15, 2017

Diagnostic ID: 24349EED-8987-48B0-87C7-F6D14028C0ED

@adrienjoly
Copy link

As posted on #2076 (comment):

Same problem on Version 17.09.1-ce-mac42 (21090), Channel: stable, 3176a6af01.

My PostgreSQL container's clock gains several seconds in the future every time I wake up my MacBook Pro from sleep. I love Docker, but having to restart it so often is really annoying...

Let me know if I can help in any way.

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants