[18.01] galaxy:galaxy_nodejs_proxy not starting due to `node` missing

[pcm32]

On 18.01 I'm getting inside supervisorctl:

galaxy:galaxy_nodejs_proxy       FATAL     Exited too quickly (process log may have details)

Upon inspection:

supervisor> tail galaxy:galaxy_nodejs_proxy
/usr/bin/env: node: No such file or directory
/usr/bin/env: node: No such file or directory
/usr/bin/env: node: No such file or directory
/usr/bin/env: node: No such file or directory

trying which node inside the running container doesn't yield anything either. Is galaxy:galaxy_nodejs_proxy still needed past 17.09, or are we missing node on the container?

Would this explain stucked URL file uploads (data pulls)? I got here due to https://github.com/galaxyproject/galaxy/issues/6319

Any thoughts @bgruening? Thanks!

[bgruening]

I think the node installation changed in the similar way than Docker, I fixed something similar in 18.05. If we agree on spinning up a branch for you to support 18.01 we should backport also the node fixes from 18.05 (in ansible-extras).