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

Shinyproxy to launch jupyter notebook with docker? #174

Closed
thomas-chauvet opened this issue Sep 13, 2019 · 7 comments
Closed

Shinyproxy to launch jupyter notebook with docker? #174

thomas-chauvet opened this issue Sep 13, 2019 · 7 comments
Milestone

Comments

@thomas-chauvet
Copy link

Hello,

As you did for zeppelin notebook, is there a way to serve jupyter notebook with Shinyproxy ?

I tried with:

specs:
    id: jupyter-notebook
    display-name: jupyter-notebook
    description: Jupyter Notebook is a web-based interactive computational environment for creating Jupyter notebook documents.
    container-cmd: ["jupyter", "notebook","--NotebookApp.token=''","--NotebookApp.password=''", "--ip=0.0.0.0", "--port=8888", "--allow-root"]
    container-image: jupyter/datascience-notebook
    container-network: shinyproxy-network
    port: 8888

Bit without success. I just have a 404..

Thanks for your help :)

@ekoepplin
Copy link

ekoepplin commented Sep 23, 2019

@thomas-chauvet did you figure it out? Just struggle with the same error Message: Not Found

id: jupyterlab
    display-name: Jupyter Lab
    description: Jupyter data science environment
    container-network: sp-example-net
    container-cmd: ["start.sh","jupyter", "lab","--LabApp.token=''","--LabApp.ip='0.0.0.0'","-- LabApp.allow_origin='same'"]
    container-volumes: [ "/home/users/#{proxy.UserId}:/home/#{proxy.UserId}" ]
    container-image: jupyter/datascience-notebook
port: 8888

where docker run -it --rm -p 8888:8888 jupyter/datascience-notebook start.sh jupyter lab --LabApp.token='' --LabApp.ip='0.0.0.0' --LabApp.al low_origin='same' runs without issues

@tverbeke
Copy link
Member

@thomas-chauvet @hugeme Jupyter notebooks don't support relative URLs, but use root-relative URLs; this means these notebooks cannot be run out of the box on ShinyProxy without working around this limitation inside ShinyProxy.

@countzero2323
Copy link

Hi, I have the same Problem.. I followed another github-project where this was realized (https://github.com/rkingdc/datascience-portal) but I get a 404, too.. Seems to me, that something happened to the jupyter-end?

 - id: jupyterlab
    display-name: Jupyter Lab 
    description: Jupyter data science environment
    container-network: sp-net
    container-cmd: ["start.sh", 
      "jupyter", "lab", 
      "--LabApp.token=''", 
      "--LabApp.ip='0.0.0.0'",
      "--LabApp.allow_origin='same'"]
    container-volumes: [ "/home/users/#{proxy.UserId}:/home/#{proxy.UserId}" ]
    container-image: jupyter  
    container-env:
      USER: root
      NB_USER: '#{proxy.UserId}'
      NB_UID: 1010
      NB_GID: 1020
      CHOWN_HOME: 'yes'
      CHOWN_HOME_OPTS: -R
    port: 8888

@mversiani
Copy link

mversiani commented May 7, 2021

Hi, is there any update on this issue? It would be great if we can run Jupyter dockers inside ShinyProxy. Regards

@LEDfan
Copy link
Member

LEDfan commented May 21, 2021

The next version of ShinyProxy will have support for running Jupyter notebooks! I created a snapshot release, so that you can already test it. See the dedicated repository for more information: https://github.com/openanalytics/shinyproxy-jupyter-notebook-demo

@LEDfan LEDfan added this to the Next milestone May 21, 2021
@LEDfan
Copy link
Member

LEDfan commented Nov 5, 2021

ShinyProxy 2.6.0 (ContainerProxy 0.8.10) has just been released with support for Jupyter Notebooks. See the demo https://github.com/openanalytics/shinyproxy-jupyter-notebook-demo

Thank you for the suggestion!

@LEDfan LEDfan closed this as completed Nov 5, 2021
@thomas-chauvet
Copy link
Author

Awesome ! Thanks !

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

6 participants