Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose Jupyter Notebook IP address to 0.0.0.0? #244

Open
isVoid opened this issue Aug 10, 2022 · 3 comments
Open

Expose Jupyter Notebook IP address to 0.0.0.0? #244

isVoid opened this issue Aug 10, 2022 · 3 comments

Comments

@isVoid
Copy link

isVoid commented Aug 10, 2022

Hi, I need to setup the cluster in a remote server and access it from a local machine. Currently the notebook IP address is set to the loopback address and prevents external user from accessing. How to expose it for remote accessing?

@jacobtomlinson
Copy link
Member

I think you need to set jupyter.args to --ip 0.0.0.0.

Which docker images are you using? The defaults or are you testing with RAPIDS?

@isVoid
Copy link
Author

isVoid commented Aug 10, 2022

I was using the default images.

@jacobtomlinson
Copy link
Member

Ok cool, I'm going to transfer this to the Dask Docker repo then as it seems to be a problem with the image rather than the helm chart.

If you think other folks might run into this we may want to explicitly bind to 0.0.0.0 in the Dask Notebook image.

exec start.sh jupyter lab --NotebookApp.base_url="${NB_PREFIX:-/}" ${JUPYTERLAB_ARGS}

In the RAPIDS images we set a bunch of sensible options, maybe we should do the same for Dask.

@isVoid do you have any interest in opening a PR?

@jacobtomlinson jacobtomlinson transferred this issue from dask/helm-chart Aug 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants