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
Race condition with lxc-info #4298
Comments
I just realised that this is a dup of #3824, please close one of them as you feel appropriate (this issue has more details about actual problem while the former has a bit more overall debugging details). |
Upgraded docker to 0.8.1, failed to start containers at all. Downgraded lxc to 0.9, seem to be working in this combo for now. |
@farcaller, your dup hyperlink links back to this same issue, #4298. ;) I think I'm having this same issue as well. Thank you very much for the |
That's done it. Thanks man, you just saved me a good number of hours! |
@farcaller Thanks for the info on lxc! |
Closing because it looks like this is resolved, probably a version conflict with what version of LXC docker supported at the time. |
For a while now I have a problem starting docker containers. It was flaky at first, now I hit the problem in 95% of container starts (I guess that might be related to my switch to raid1 on mmcblks, that slowed I/O even more).
docker version:
Problem:
Docker log:
.dockerinit is confirmed to run up to exec (additional logging to fs, as nothing else seems to be reachable).
I traced the problem up to
lxc-info
run, which is hard to debug further. My wrapper scriptprevents the problem from happening. Well, even the simplest
sleep 1
fixes it, actually.I guess that either
waitForStart
logic is broken somehow, or there must be a better trigger criteria to detect "container not booted yet" vs "container died".The text was updated successfully, but these errors were encountered: