search

siomiz / chrome

Docker Automated Build Repository for siomiz/chrome -- Google Chrome via VNC (or via Chrome Remote Desktop)
https://hub.docker.com/r/siomiz/chrome/
MIT License
197 stars 124 forks source link

remote-debugging #26

Open PierreBrisorgueil opened 3 years ago

PierreBrisorgueil commented 3 years ago

Hey @siomiz ! thx for this work! hard to fine but very useful!

i have a quick question, i'm trying to enable chrome remote debugging and expose it but can't, it seems to activate fine but i can't expose it on docker, someone has already tried?

entrypoint.sh --remote-debugging-address=0.0.0.0 --remote-debugging-port=9222

DOCKERFILE EXPOSE 9222

EDIT : 1/ with --headless it works and is well exposed, the problem is therefore chrome side 2/ Link : https://groups.google.com/a/chromium.org/g/chromium-dev/c/CUIPzp5T5sw 3/ maybe linked to Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

LOGS :

headless remote work 

[0429/095734.842855:ERROR:chrome_main_delegate.cc(700)] Web security may only be disabled if '--user-data-dir' is also specified with a non-default value.
[231:241:0429/095734.893601:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[231:254:0429/095734.926496:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[231:254:0429/095734.926541:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[250:250:0429/095734.930396:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is egl

DevTools listening on ws://127.0.0.1:9222/devtools/browser/22cbcfe9-83ff-4c0d-8ca0-d7592206296a
[231:254:0429/095734.938176:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[231:254:0429/095734.938219:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[231:287:0429/095734.984830:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[231:287:0429/095734.984888:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[231:287:0429/095734.984931:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[231:287:0429/095734.985016:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[231:287:0429/095734.985078:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

heedful remote failed

[0429/095755.263908:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[0429/095755.266330:WARNING:headless_browser_main_parts.cc(83)] Cannot create Pref Service with no user data dir.

DevTools listening on ws://0.0.0.0:9222/devtools/browser/c5d8dacb-635f-43bf-aef0-793e6637c2f6
[0429/095755.306546:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is egl
jvitor83 commented 2 years ago

Hi @PierreBrisorgueil i tought you would like this one i created based on some research i made on the web about it (like this and others images). Take a look at this repository https://github.com/jvitor83/chrome-debug-node-vnc It is a built-in chrome with debug capabilities and VNC for remote viewer and node to use puppeteer. In some testing it isn't detected as a bot because it is headfull (but inside docker container).

PierreBrisorgueil commented 2 years ago

@jvitor83 Hey, thx for this work and share 🙏, I will have a look !