-
Notifications
You must be signed in to change notification settings - Fork 125
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 connect via VNC #28
Comments
I also can not connect. with docker logs: 2022-10-08 10:53:23,779 INFO spawned: 'chrome' with pid 245
2022-10-08 10:53:23,914 INFO exited: chrome (exit status 21; not expected)
2022-10-08 10:53:23,914 INFO gave up: chrome entered FATAL state, too many start retries too quickly
2022-10-08 10:53:23,914 INFO reaped unknown pid 247
2022-10-08 10:53:23,915 INFO reaped unknown pid 248
2022-10-08 10:53:23,915 INFO reaped unknown pid 249
2022-10-08 10:53:33,615 INFO reaped unknown pid 133
2022-10-08 10:53:33,700 INFO reaped unknown pid 131
2022-10-08 10:53:35,772 INFO reaped unknown pid 202
2022-10-08 10:53:35,844 INFO reaped unknown pid 200
2022-10-08 10:53:38,914 INFO reaped unknown pid 271
2022-10-08 10:53:38,985 INFO reaped unknown pid 269 |
@Meowzz95 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi. I have followed step 1 and then I get stuck at step 2.
I cannot connect with VNC Viewer to neither to the IPAddress 172.17.0.2 nor to 172.17.0.2:5900. Could you maybe be more specific how you would connect to the containers VNC?
Thanks in advance!
The text was updated successfully, but these errors were encountered: