Failed to start --remote-debugging-port in docker container

2,039 views
Skip to first unread message

Gaurav Aggarwal

unread,
Sep 27, 2016, 3:30:43 AM9/27/16
to Chromium-dev
I am trying to run chrome with remote debugging enabled in a Docker container and I have tried the following things:

- Xvfb for virtual display
- VNC server

Although chrome process starts, but remote debugging server is not starting. I get following error messages:

root@4f64804f45d4:/crawler/output/www.cnn.com# chromium-browser --remote-debugging-port=9222
Xlib:  extension "RANDR" missing on display ":0".
ratpoison:manage.c:236: error: XGetWMName failed
[31725:31747:0927/061155:ERROR:bus.cc(432)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Xlib:  extension "RANDR" missing on display ":0".
ratpoison:manage.c:236: error: XGetWMName failed
[31725:31725:0927/061155:ERROR:desktop_window_tree_host_x11.cc(901)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType)

There is no server running on port 9222:
root@4f64804f45d4:/crawler/output/www.cnn.com# nc -zv localhost 9222
nc: connect to localhost port 9222 (tcp) failed: Connection refused
nc: connect to localhost port 9222 (tcp) failed: Connection refused

I tried to strace the bind system call but I do not see any bind on port 9222 (I can see a bind on port 9222 while I run chrome on my desktop).

Any suggestion about how should I debug why the debug server is not starting?

Jamie Walch

unread,
Sep 27, 2016, 7:29:03 PM9/27/16
to gaurav.ag...@gmail.com, Chromium-dev
It looks like the version of Xvfb you're using doesn't support the randr extension, and something you're running requires it. I think the latest Ubuntu releases ship with a version of Xvfb that supports randr. If you can't use that, then you can build one yourself by applying this patch to the Xvfb source code: https://patchwork.freedesktop.org/patch/13852.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

Gaurav Aggarwal

unread,
Sep 28, 2016, 1:51:57 AM9/28/16
to Jamie Walch, Chromium-dev
Thanks for your response. I am able to remove randr extension error by moving to Ubuntu 16.04 and using xvfb with rndr extension eabled but the debugging server is still not coming up:

root@2a25eac733db:/crawler/src# chromium-browser --remote-debugging-port=9222 --disable-gpu&
[2] 1040
root@2a25eac733db:/crawler/src# [1040:1055:0928/054434:ERROR:bus.cc(432)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[1040:1040:0928/054434:ERROR:desktop_window_tree_host_x11.cc(901)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType

root@2a25eac733db:/crawler/src# nc -zv localhost 9222
localhost [127.0.0.1] 9222 (?) : Connection refused

Any suggestion is welcome.

Thanks once again.

On Tue, Sep 27, 2016 at 4:28 PM, Jamie Walch <jamie...@chromium.org> wrote:
It looks like the version of Xvfb you're using doesn't support the randr extension, and something you're running requires it. I think the latest Ubuntu releases ship with a version of Xvfb that supports randr. If you can't use that, then you can build one yourself by applying this patch to the Xvfb source code: https://patchwork.freedesktop.org/patch/13852.

On Tue, Sep 27, 2016 at 12:30 AM, Gaurav Aggarwal <gaurav.ag...@gmail.com> wrote:t 
Reply all
Reply to author
Forward
0 new messages