Running recent nightly version of Slicer with GUI

[lassoan]

I'm trying to run a recent nightly version of Slicer with GUI using Docker on Windows.

This image works fine - I open http://localhost:32768 and can interact with Slicer in a browser. However, it's an ancient Slicer version:
https://hub.docker.com/r/dit4c/dit4c-container-slicer/

I've tried to run slicer/slicer-test:opengl but I cannot connect to it through the browser: http://localhost:(portnumber) gives "can't reach this page" error. Error log:

2017-09-25 14:31:19,851 CRIT Supervisor running as root (no user in config file)
2017-09-25 14:31:19,851 INFO Included extra file "/etc/supervisor/conf.d/graphical-app-launcher.conf" during parsing
2017-09-25 14:31:19,851 INFO Included extra file "/etc/supervisor/conf.d/noVNC.conf" during parsing
2017-09-25 14:31:19,851 INFO Included extra file "/etc/supervisor/conf.d/x11vnc.conf" during parsing
2017-09-25 14:31:19,851 INFO Included extra file "/etc/supervisor/conf.d/xdummy.conf" during parsing
2017-09-25 14:31:19,857 INFO RPC interface 'supervisor' initialized
2017-09-25 14:31:19,857 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2017-09-25 14:31:19,857 INFO supervisord started with pid 1
2017-09-25 14:31:20,858 INFO spawned: 'graphical-app-launcher' with pid 7
2017-09-25 14:31:20,859 INFO spawned: 'noVNC' with pid 8
2017-09-25 14:31:20,860 INFO spawned: 'xdummy' with pid 9
2017-09-25 14:31:20,861 INFO spawned: 'x11vnc' with pid 10
2017-09-25 14:31:20,921 INFO success: graphical-app-launcher entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-09-25 14:31:20,968 INFO exited: xdummy (exit status 0; not expected)
2017-09-25 14:31:21,947 INFO success: noVNC entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-09-25 14:31:21,948 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-09-25 14:31:22,014 INFO spawned: 'xdummy' with pid 143
2017-09-25 14:31:22,016 INFO waiting for graphical-app-launcher, noVNC, xdummy, x11vnc to die
2017-09-25 14:31:22,016 INFO stopped: x11vnc (terminated by SIGTERM)
2017-09-25 14:31:22,017 INFO stopped: xdummy (terminated by SIGTERM)
2017-09-25 14:31:22,020 INFO stopped: noVNC (exit status 143)
2017-09-25 14:31:22,020 INFO reaped unknown pid 144
2017-09-25 14:31:22,029 INFO reaped unknown pid 119
2017-09-25 14:31:22,149 INFO stopped: graphical-app-launcher (exit status 143)

[thewtex]

The output looks good, but we may need to update the instructions for working with Docker for Windows to replace localhost with a different host / value. See for example:

https://blog.sixeyed.com/published-ports-on-windows-containers-dont-do-loopback/

[lassoan]

I've tried to enter the host name and IP address and also trying to access from external network but it had the same error as with localhost.

Could the same mechanism implemented as in dit4c? That works well in Windows.

[thewtex]

It uses a similar architecture as dit4c, but slicer/slicer-test:opengl is configured for running the tests, which may explain the behavior.

[lassoan]

Would it be possible to create another image that could be used similarly to dit4c? I would like to show recent Slicer feature to people without requiring them to install Slicer.

[thewtex]

I'll take a look...

[jcfr]

as a side note:

• I just published the scripts we use to update the Slicer docker images: https://github.com/Slicer/SlicerDockerUpdate
• to address this, I added a step to remove dangling images. We ran out of space on the build machine (see remove-dangling-images.sh and update-build-publish.sh#L80)