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

Docker CLI ceased working #238

Closed
joconor opened this issue Aug 11, 2016 · 4 comments
Closed

Docker CLI ceased working #238

joconor opened this issue Aug 11, 2016 · 4 comments

Comments

@joconor
Copy link

joconor commented Aug 11, 2016

Expected behavior

docker-compose stop works

Actual behavior

docker-compose & docker ps just hang

Information

Diagnostic ID: D4F0D98E-8F73-4F24-B486-7A43E779721D
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[ERROR] docker-cli
docker ps failed
[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

Not sure if there's a connection, but this occurred when I wanted to shut down my docker stack (via docker-compose down) after being prompted about the existence of an update. I dismissed the update via 'Remind Me Later' then attempted docker-compose down.

@mchiang0610
Copy link

merging with #119

@samoht
Copy link
Contributor

samoht commented Oct 12, 2016

Detected symptom of problem 'invariant-violated' in tmp/20160714-163824.

An invariant within the code of one of the components was not held. Docker needs to be restarted.

May be related to #89

The following log matches:

Jul  7 17:14:24 Jays-CC-MBP Docker[com.docker.osxfs][27759] <Notice>: Volume.stop ce031432a097b155ee4d5e473cd0f676d4cf0cb2037ef3412cea28f28200800d (paths = [/Users/Jay/ClearCareRepos/clearcare/docker/logger/fluent.conf])
Jul  7 17:14:36 Jays-CC-MBP Docker[com.docker.osxfs][27759] <Notice>: Volume.stop c96e3d0c17d54a7418ed66d28d31e210314f16afede8794e934f6302ab98e154 (paths = [/Users/Jay/ClearCareRepos/clearcare])
Jul  7 17:14:36 Jays-CC-MBP Docker[com.docker.osxfs][27759] <Error>: WATCH TREE REMOVAL EXISTENCE INVARIANT VIOLATED
Jul  7 17:14:42 Jays-CC-MBP Docker[com.docker.osxfs][27759] <Notice>: Creating resource Entry(f2cce8e31b5ab32db9ee520987797b48d6fd110297e5875a6d3cf25a3effa230)
Jul  7 17:14:42 Jays-CC-MBP Docker[com.docker.osxfs][27759] <Notice>: Write offset=0 data=[f2cce8e31b5ab32db9ee520987797b48d6fd110297e5875a6d3cf25a3effa230:clearcare_cc_dynamodb] to file
Jul  7 17:14:42 Jays-CC-MBP Docker[com.docker.osxfs][27759] <Notice>: Volume.start f2cce8e31b5ab32db9ee520987797b48d6fd110297e5875a6d3cf25a3effa230 (paths = [clearcare_cc_dynamodb])

/cc @dsheets

@dsheets
Copy link
Contributor

dsheets commented Nov 2, 2016

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!

@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 18, 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

6 participants