-
Notifications
You must be signed in to change notification settings - Fork 118
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
Docker Crashes and Restarts in unstable state #289
Comments
I'm witnessing the same behaviour, same software versions as the parent poster. |
Exactly the same issue. Could be related to moby/moby#24045 |
the same issue. |
There have been some improvements to the vsock code in the 1.12.1-beta27 release so if you are happy trying a beta version of the software it would be useful to know if this has resolved it for you. When switching between the beta and stable branches it is necessary to uninstall Docker for mac. If it still occurs for any of you with beta27 please open fresh individual tickets against https://github.com/docker/for-mac with the full output of diagnostics (from the whale menu). Providing reproduction steps of any case would also be very useful in tracking this down. I understand that many of the repro cases are when building proprietary software but if someone was able to par their case down to just the basic build system skeleton required to trigger the issue (removing all the proprietary stuff) or find a subset of their code which they were willing/able to post then we'll stand a much better chance of nailing this once and for all. |
Detected symptom of problem 'invariant-violated' in F9B62D2C-58B4-4D3D-99AF-6247680F0C16/20160815-153602. An invariant within the code of one of the components was not held. Docker needs to be restarted. Please upgrade to a more recent version of Docker which fixes this issue with osxfs. May be related to #89 The following log matches:
/cc @dsheets |
This invariant violation was a symptom of a use-after-free bug in the file system event watching code which occurred due to multiple containers with volume mounts racing to set up their mounts. It is possible that it caused your hangs or crashes and has been fixed in the recently released Beta 29.3. Please open a new issue for any further problems. Thanks! |
Closed issues are locked after 30 days of inactivity. 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. |
Expected behavior
Use Docker normally: 'docker-compose up' to launch all machines (web, worker, db, redis)
Make code changes, web server restarts and reloads updated code.
Actual behavior
Occasionally, the web server bombs out with a console log like the following:
Information
Diagnostic ID: F9B62D2C-58B4-4D3D-99AF-6247680F0C16
Docker for Mac: 1.12.0-a (Build 11213)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[OK] app
[OK] moby-syslog
[OK] disk
[OK] virtualization
[OK] system
[OK] menubar
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux
Steps to reproduce
Pasting contents of system console log for Docker events:
The text was updated successfully, but these errors were encountered: