Closed johrstrom closed 2 years ago
@johrstrom Sounds good. Do we need to patch bc_desktop to not use the nohttpd flag? or do we need to patch TurboVNC? It wasn't quite clear on which app needs patching.
I think we can downgrade turbovnc or patch one of our libraries (basically just drop a new file in the container and/or sed -i
).
I think we can downgrade turbovnc or patch one of our libraries (basically just drop a new file in the container and/or
sed -i
).
Sounds good. Let's patch one our libraries as there are no arm64 builds for TurboVNC versions 2.2.x so we can't downgrade. They only provide arm64 builds for TurboVNC >3.0. Which files need the sed -i
patch?
This is my built from source location.
[hpcadmin@ondemand ~]$ grep -r httpd /usr/share/gems/gems/ood_core-0.19.0/
/usr/share/gems/gems/ood_core-0.19.0/lib/ood_core/batch_connect/templates/vnc.rb: VNC_OUT=$(vncserver -log "#{vnc_log}" -rfbauth "#{vnc_passwd}" -nohttpd -noxstartup #{vnc_args} 2>&1)
Here's the location of an RPM install. The versions in the directory path could change. We may end up with OOD 2.0.27
which uses 0.19.0
as above.
[johrstrom ~()] grep -r httpd /opt/ood/ondemand/root/usr/share/gems/2.7/ondemand/2.0.23/gems/ood_core-0.18.1/
/opt/ood/ondemand/root/usr/share/gems/2.7/ondemand/2.0.23/gems/ood_core-0.18.1/lib/ood_core/batch_connect/templates/vnc.rb: VNC_OUT=$(vncserver -log "#{vnc_log}" -rfbauth "#{vnc_passwd}" -nohttpd -noxstartup #{vnc_args} 2>&1)
Desktops don't work because they fall victim to https://github.com/OSC/ood_core/issues/737 which I figure we should just drop-in patch in the image?