bobbintb Posted July 17, 2020 Share Posted July 17, 2020 (edited) I am trying to create a docker for rmlint. I'm so close but keep getting an error: 2020-07-17 00:50:30,527 INFO supervisord started with pid 1 2020-07-17 00:50:30,527 INFO supervisord started with pid 1 2020-07-17 00:50:31,528 INFO spawned: 'easy-novnc' with pid 15 2020-07-17 00:50:31,528 INFO spawned: 'easy-novnc' with pid 15 2020-07-17 00:50:31,529 INFO spawned: 'app' with pid 16 2020-07-17 00:50:31,529 INFO spawned: 'app' with pid 16 2020-07-17 00:50:31,531 INFO spawned: 'openbox' with pid 17 2020-07-17 00:50:31,531 INFO spawned: 'openbox' with pid 17 Listening on http://:8080 Run with --help for more options 2020-07-17 00:50:32,634 INFO success: easy-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-07-17 00:50:32,634 INFO success: easy-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-07-17 00:50:32,634 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-07-17 00:50:32,634 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-07-17 00:50:32,634 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-07-17 00:50:32,634 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Openbox-Message: Failed to open the display from the DISPLAY environment variable. 2020-07-17 00:50:32,895 INFO exited: openbox (exit status 1; not expected) 2020-07-17 00:50:32,895 INFO exited: openbox (exit status 1; not expected) Unable to init server: Could not connect: Connection refused 2020-07-17 00:50:33,208 INFO spawned: 'openbox' with pid 24 2020-07-17 00:50:33,208 INFO spawned: 'openbox' with pid 24 Openbox-Message: Failed to open the display from the DISPLAY environment variable. 2020-07-17 00:50:33,223 INFO exited: openbox (exit status 1; not expected) 2020-07-17 00:50:33,223 INFO exited: openbox (exit status 1; not expected) Unable to init server: Could not connect: Connection refused 00:50:33 INFO [__init__.py: 42] root: Starting up. Unable to init server: Could not connect: Connection refused (shredder:16): Gtk-WARNING **: 00:50:33.440: cannot open display: :0 2020-07-17 00:50:33,443 INFO exited: app (exit status 1; not expected) 2020-07-17 00:50:33,443 INFO exited: app (exit status 1; not expected) 2020-07-17 00:50:34,444 INFO spawned: 'app' with pid 28 2020-07-17 00:50:34,444 INFO spawned: 'app' with pid 28 2020-07-17 00:50:34,445 INFO spawned: 'openbox' with pid 29 2020-07-17 00:50:34,445 INFO spawned: 'openbox' with pid 29 Openbox-Message: Failed to open the display from the DISPLAY environment variable. 2020-07-17 00:50:34,459 INFO exited: openbox (exit status 1; not expected) 2020-07-17 00:50:34,459 INFO exited: openbox (exit status 1; not expected) Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused 00:50:34 INFO [__init__.py: 42] root: Starting up. Unable to init server: Could not connect: Connection refused (shredder:28): Gtk-WARNING **: 00:50:34.574: cannot open display: :0 I used these instructions as a template: https://www.digitalocean.com/community/tutorials/how-to-remotely-access-gui-applications-using-docker-and-caddy-on-ubuntu-18-04#step-2-—-setting-up-the-openbox-menu My docker file is here: https://github.com/bobbintb/docker-rmlint It can also be installed with CA and enabling the docker hub. I started with the tutorial and got Thunderbird working just fine. I just made a few changes to get rmlint to work but that's when I got the error. Maybe I'm missing something but I thought this would be a good place to ask. Once I finish this issue, I should be able to publish it to CA. Edited July 17, 2020 by bobbintb Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.