-
Notifications
You must be signed in to change notification settings - Fork 368
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
PID Judge comes too fast results in premature kill. #526
Comments
There is no option yet to adjust the timeout. Line 8345 in cb29a99
Instead of
It is not a nice way, but the only one I found so far. |
So sad that I got this from a package manager. I'm pretty much unable to write to such scripts manually...... Actually I don't think this issue is even prevalent or whatsoever. I have a decent desktop, wonder why docker started so slow...... Currently I'm doing it the crude way and it worked quite well...... |
I've came to a pretty intriguing bug up here:
At first running containers failed with the following error:
After enabling verbose I found that the script repeatedly checks if any PID is received.
After some attempts I got one running successfully out of pure luck.
I found out AFTER the window appeared and BEFORE anything shows up in the window, if I suspend the x11docker process for some time, during which I guess docker is starting, and I run fg to bring the process back, the container can startup normally.
Is there an option to manually adjust the timeout?
I guess we should use some other mechanisms to determine if a docker container have been started up or not, instead of using PID and a timeout?
The text was updated successfully, but these errors were encountered: