Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
nigeilN

nigeil

@nigeil
About
Posts
1
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Accessing mounted volumes in jupyter notebooks
    nigeilN nigeil

    I have been attempting to provide access to a cloudron volume to users working with jupyterhub.

    I have been able to mount the volume to the jupyterhub parent container through the cloudron web interface, and can access it from the web debugging terminal under /media/ as expected.

    However, the volume is not accessible in the spawned jupyterlab instances, either under /media/ or /home/jovyan/ (the default home directory in spawned jupyterlab containers).

    Digging through some of the code that is generated at run-time to spawn jupyterlab containers (such as /run/jupyterhub/config), I do not see any mention of mounting the directories under /media/ to the child containers.

    I imagine the parent container (the jupyterhub server that cloudron directly manages) will need to mount the shared volume to the jupyterlab containers it spawns. However I am not sure how to accomplish this.

    I appreciate any thoughts/guidance cloudron users and staff might have - thank you!

    JupyterHub
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search