Well, headway I guess. I can get the job running on the host with a button created, which launches another browser tab that does show a noVNC window, but it “Failed to connect to server”. Here’s the URL the button points to:
https://<client_host>/pun/sys/dashboard/noVNC-1.1.0/vnc.html?utf8=%E2%9C%93&autoconnect=true&path=rnode%2F<exec_host>%2F22793%2Fwebsockify&resize=remote&password=RKov4wP9&compressionsetting=6&qualitysetting=2&commit=Launch+Relion3
looks ok to my untrained eyes. I had to cheese the process a little and run the websockify_cmd in my template/script.sh.erb to get around the “find_port” issue.
on further review, I’m returning to port mismatch. If websockify is the way from the client -> vncserver it can’t get there because the server started on port 5901 but the docker container’s exposed port is 8719. websockify is mapped correctly into the container but the server inside is not running on that port. I don’t see a way to tell vncserver which port to use when it starts.