search

IBM / StorageScaleVagrant

Example scripts and configuration files to install and configure IBM Storage Scale in a Vagrant environment
Apache License 2.0
16 stars 19 forks source link

GUI access via localhost:8888 clashes if Jupyter Notebooks is also installed. #54

Open dannyk96 opened 5 days ago

dannyk96 commented 5 days ago

Many people use Jupyter Notebooks on their desktop systems This out of the box uses localhost:888 ref: https://docs.jupyter.org/en/latest/running.html

This creates a clash with any attempt to reach the Spectrum Scale GUI on the same machine.

If you don't want to change:

node.vm.network "forwarded_port", guest: 443, host: 8888

then perhaps some warning could be added to the documentation? (In my case I had been running some Jupyter notebook a week previously and couldn't work out why I could not longer provison a Scale VM using Vagrant and use the GUI)

hseipp commented 5 days ago

Thank you @dannyk96 for pointing this out.

If you search the main README for 8888, you will notice four hits plus various occurrences in the screenshots so the fact that port 8888 is used is visible in the documentation.

But I am getting your point and will add a hint that the GUI port that is being exposed to the host can be adjusted like you showed above in case you need other applications to use that port.

I won't choose another port as default as this will not solve the general problem. You'll always find another application that might use exactly that other port. And ... you could also run the Jupyter notebook server on another port ;-)

dannyk96 commented 4 days ago

I was fully aware that the Scale VM uses port 8888 to redirect to the GUI. however I 'forgot' that I had also been using Jupyter Notebooks a few weeks ago. I was failing to reach the Scale VM's GUI and so was resorting to manually going into VirtualBox to add an extra port forwarding of port 8889 to the VM's port 443 while I was trying to guess where the problem with port 8888 was coming from. It was only when I was doing something else that required a Jupyter notebook that I spotted the port clash. Doh!

So if you don't want to change the port (to say 8443), I was going to suggest a comment in your README to warn that the widely used Jupyter Notebooks also uses port 8888 and so need to edit the Vagrantfile to use something else (like 8889 or 8443) ?

hseipp commented 3 days ago

So if you don't want to change the port (to say 8443), I was going to suggest a comment in your README to warn that the widely used Jupyter Notebooks also uses port 8888 and so need to edit the Vagrantfile to use something else (like 8889 or 8443) ?

I won't change the port to 8443 as IBM Storage Ceph that I'm running in separate VMs (see my other project) is using that port for the GUI.

But as I said above, I agree on better documenting the port usage and how to change it. Is is on my To-Do list for the next release.

dannyk96 commented 22 hours ago

hmm. Collision with Ceph is also not good either. Looks at the docs there is already an auto correct feature: https://developer.hashicorp.com/vagrant/docs/networking/forwarded_ports#auto_correct

As a change request, could this be added to the port forwarding line in the Vagrantfile?