rkingdc / datascience-portal

Use shinyproxy to achieve Rstudio Server Pro feature parity
https://www.rkingdc.com/blog/2019/3/27/approximating-rstudio-server-pro-and-shiny-server-pro-and-jupyterhub-for-free
17 stars 11 forks source link

Running jupyter notebook / lab #1

Open thomas-chauvet opened 5 years ago

thomas-chauvet commented 5 years ago

Hello,

I struggle to launch jupyter within Shinyproxy even with the docker-compose provided in this repository. I have a 404 error when I try to launch jupyter.

Is there something special to know ?

I also opened an issue on Shinyproxy repo.

Thanks,

Thomas

leungi commented 4 years ago

Same issue.

Running jupyter container stand-alone is not working either.

PS P:\> docker run jupyter
Set username to: jovyan
usermod: no changes
Executing the command: jupyter lab --LabApp.token='' --LabApp.ip='0.0.0.0' --LabApp.allow_origin='same'
[I 21:17:46.519 LabApp] Writing notebook server cookie secret to /home/jovyan/.local/share/jupyter/runtime/notebook_cookie_secret
[W 21:17:46.700 LabApp] All authentication is disabled.  Anyone who can connect to this server will be able to run code.
[I 21:17:46.709 LabApp] JupyterLab extension loaded from /opt/conda/lib/python3.7/site-packages/jupyterlab
[I 21:17:46.709 LabApp] JupyterLab application directory is /opt/conda/share/jupyter/lab
[I 21:17:46.711 LabApp] Serving notebooks from local directory: /home/jovyan
[I 21:17:46.711 LabApp] The Jupyter Notebook is running at:
[I 21:17:46.711 LabApp] http://dcbdccf63bfb:8888/
[I 21:17:46.711 LabApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).

Trying localhost:8888 or using the listed http://dcbdccf63bfb:8888/ above doesn't load jupyter.

rkingdc commented 4 years ago

Sorry about the slow response here! I never got a notification about this. I haven't looked at this in a while, but I remember seeing this issue too. I was able to track down and understand the issue, but not the fix. If you open up developer tools and wand watch the requests that get made when you launch the jupyter app, you can see that the first request is to a jupyter endpoint than then issues a HTTP 300 redirect. The URL to redirect to isn't constructed correctly, since jupyter is expecting a relative URL.

I think that a fix could be implemented in the nginx config file to make sure that the redirect writes the URL correctly, but I was never able to figure out what that fix is. If you know any nginx wizards, I'd guess they could fix this fairly easily.

leungi commented 4 years ago

Thanks for looking into @rkingdc; with reference to #2, it seems we both have issues with running Jupyter in shinyproxy.

I'll let you decide if you want to close this 😊

zhiboz commented 3 years ago

any update on this? I'm hitting 404 error when trying to launch jupyterlab as well.