Skip to content
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

Google Chrome doesn't run solo #24

Open
llimllib opened this issue Apr 4, 2017 · 2 comments
Open

Google Chrome doesn't run solo #24

llimllib opened this issue Apr 4, 2017 · 2 comments

Comments

@llimllib
Copy link

llimllib commented Apr 4, 2017

I expect this command to print out the HTML of a website:

docker-chromium-xvfb/images/base $ docker build -t chromium-xvfb . && docker run --rm --security-opt seccomp=unconfined chromium-xvfb /usr/bin/google-chrome --disable-gpu http://google.com

Instead, it just hangs. The run command outputs this information:

Xlib:  extension "RANDR" missing on display ":99".
[6:17:0404/164119.237190:ERROR:bus.cc(427)] 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 ":99".

and the image has to be killed via docker kill. I can get rid of the dbus error with:

docker run --rm --security-opt seccomp=unconfined chromium-xvfb bash -c 'service dbus start && /usr/bin/google-chrome --disable-gpu http://google.com'

But I still just get a hung docker image. I've tested replacing http://google.com with a local URL and --net=host to ensure that it's not hitting the server, and it's not.

Any ideas for how I could get this to work, or to debug it further?

@nikkwong
Copy link

Were you able to figure this out?

@llimllib
Copy link
Author

nope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants