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
Cannot start VNC container but logs show it's connected #2063
Comments
FTR we keep having the issue, with the same long trace of logs from VNC container, proving that it started. Right now it prevents some of our tests to execute since the container is considered as "not started" and it fails entirely the test suite. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this. |
This issue has been automatically closed due to inactivity. We apologise if this is still an active problem for you, and would ask you to re-open the issue if this is the case. |
…s#2063) (testcontainers#2547) Co-authored-by: Stefan Rempfer <srempfer@rt.ipnt.de> Co-authored-by: Richard North <rich.north@gmail.com> Co-authored-by: Sergei Egorov <bsideup@gmail.com>
We recently have a new kind of issue with VNC container which is flickering: most of the time it works properly, but from time to time we obtain a
What's surprising is that according to the source,
waitUntilReady
is actually waiting forConnected
:testcontainers-java/core/src/main/java/org/testcontainers/containers/VncRecordingContainer.java
Line 74 in 92f0a4f
and according to the logs we got after the stacktrace, VNC was indeed connected:
Not sure what could be related to the issue? The fact that it happens only from time to time, makes me think that it could be a kind of race condition.
For info we are using latest release of testcontainers (1.12.3) and we are running it inside a customized jenkins docker container (docker inside docker).
Here's the full stacktrace and the beginning of the VNC logs (too long to put them all, and they don't provide any more info):
The text was updated successfully, but these errors were encountered: