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

Please help me understand docker GUIs. #492

Firedrops opened this issue Aug 3, 2019 · 1 comment


Copy link

commented Aug 3, 2019

Thank you for your 'rambles' and examples, they were great to get started with. I have been using your jess/chrome to try stuff. It works by itself. However, a lot of things weren't explained.

  1. Besides the parameters tacked onto docker run, are there specific things you need to install/configure in the dockerfile to enable the GUI functionality?

  2. If I wish to adapt it such that the docker runs in the terminal window as usual, and at a point when the user wishes, analogous to how a lay-user decides when to open chrome by clicking on it manually, how can I do that?
    /bin/bash -c "google-chrome" returns

[8459:8459:0803/] Running as root without --no-sandbox is not supported. See

is this an error specific to chrome?

My end goal is to have R/R-studio and Circos usable in a docker container, opening a GUI window when used. I have already found a resource that gives R an interface through the browser, but haven't found something like that for Circos. Is this a feasible task?


This comment has been minimized.

Copy link

commented Aug 3, 2019

Issue-Label Bot is automatically applying the label question to this issue, with a confidence of 0.83. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the question label Aug 3, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.