Issue Setting up docker image and connecting both VNC and Remote Debugging
Hey everyone! đź‘‹
I'm running into some trouble getting VNC to connect to my Docker container. Using apify/actor-node-playwright-chrome and running it as-is, but no luck in headful mode. The chrome_test.js and main.js run perfectly but VNC and Remote Debugging is not working.
I'm on windows 11, using vscode, wsl2, docker-desktop.I tried pulling the image from docker repo but then, I built the image on Ubuntu distro via WSL2 and Doker-Desktop with WSL integration enabled.
Here’s what I’ve tried so far:
Modified chrome_test.js to add a delay when headless: false
Exposed the necessary ports
Removed -nolisten tcp from both VNC servers
Still can’t connect via VNC (RealVNC) or Chrome Remote Debugging
Is the image missing something like a vnc server?
Does the xvfb/xvfb-run serves as the vnc server. Cause it usually used with a vnc server like X11vnc.
I exposed as will Chrome Remote Debugging port with out a success to establish a connection.
Not sure what I’m missing. Trying to set up Docker properly before diving into actor development. Anyone run into this before? Would appreciate any tips! 🙏
3 Replies
Someone will reply to you shortly. In the meantime, this might help:
exotic-emerald•2mo ago
Hi,
Could you provide an error trace? How exactly does it fail?
It will be easier to help once I have more details about your logs and the exact errors. Once I have that, I can check with our engineering team.
In the meantime, you can find more info about Apify's Docker images here:
Apify Docker Images
Could you provide an error trace? How exactly does it fail?
It will be easier to help once I have more details about your logs and the exact errors. Once I have that, I can check with our engineering team.
In the meantime, you can find more info about Apify's Docker images here:
Apify Docker Images
extended-salmonOP•2mo ago
Hey @Oleg V.
Thanks for your response and for offering to help—I really appreciate it.
It's not an error; the issue is that the VNC client fails to connect when I try to test healfull (with Headless = false). Additionally, Remote Debugging does not work once I run the container, even though I have exposed the necessary ports.
While I document a more detailed, step-by-step breakdown of what I did, could you test the image itself? Specifically, try running Remote Debugging and connecting via the VNC client. If you succeed—not just in running the container and testing the scripts, but also in establishing the VNC and Remote Debugging connections—then the issue must be on my end.
Note: Since the embedded test script included with the image only takes a few minutes to run, I recommend either modifying it to run longer or adding your own script to properly test VNC and Remote Debugging connections.
Regards