Closed gidfiddle closed 5 years ago
Thank you for reporting!
I cannot explain why a delay is necessary here even after the container has been determined to be "ready" because the test $Dockerexe exec $Containername sh -c : has succeeded.
That is odd, indeed. I have made a commit with a repeated check like in your proposal, it should work now. Please try out.
Thanks for a great piece of software.
:-)
x11docker --version: 5.4.4
On a rather slow Ubuntu 18.04 machine, the command
always fails with a "Container startup seems to have failed." error, despite (usually) working well on a faster Fedora 29 machine. I traced the problem to the following statement in the x11docker script:
sets Pid1pid to zero. I succeeded in working around this problem by putting this line in a loop like another one in the script:
(The first test is needed because Fedora sometimes sets Pid1pid to a blank.) One pass through the loop usually suffices to get a valid Pid1pid.
I cannot explain why a delay is necessary here even after the container has been determined to be "ready" because the test
has succeeded.
Could you please look into this issue and make an appropriate correction?
Thanks for a great piece of software.