Skip to content

europlanet-gmap/docker-jupyterhub

 
 

Repository files navigation

Docker JupyterHub

This setup of JupyterHub provides a Docker-based reference deployment, it is a customization for the use-cases of planetary data scientists in the context of the Europlanet GMAP project. The work is based on Jupyter's jupyterhub-deploy-docker.

This deployment include users authentication through Gitlab/Github systems, multiple choices of Jupyter Lab environments through Docker images, multiple storage spaces for private and shared data, and user initialization script/hooks for live, pre-login environment management.

The Notebook images we use by default here are those provided by GMAP through DockerHub at:

  • hub.docker.com/u/gmap

    • jupyter-isis-asp
    • jupyter-isis
    • jupyter-gispy

    These images are meant to be used in a JupyterHub setup like this as well as standalone, autonomously, without a JupyterHub server. Their source code is provided at GMAP GitHub organization at:

In the docs you'll find detailed information on how to change the list of images in your deployment, any image base on the official Jupyter Docker Stack images should just work.

Prerequisites

Docker

This deployment uses Docker, via Docker Compose, for all the things.

Run the default setup

To run the JupyterHub with the default Notebook images:

  1. Pull Notebook images
  2. Run JupyterHub
    • access the service in your browser
    • shutdown the service when done

Per default, a ./tmp directory will be created in your current working directory to provide the necessary host-container directories structure for it to run properly. Those directories can be properly defined in env.notebook.

Pull Notebook images

The Notebook (aka, singleuser) images available to the users should be available in disk beforehand. A convenience script, setup.sh, is provided to simplify setting up the system.

To pull the images defined here by default, just do:

# cd docker/
./setup.sh --pull-notebook-images

Run JupyterHub

Run the JupyterHub container on the host.

To run the JupyterHub container in detached mode:

docker-compose up -d

Once the container is running, you should be able to access the JupyterHub console at

http://localhost:8000

To bring down the JupyterHub container:

docker-compose down

Build JupyterHub/Notebook images

I invite you to read the details about building images (and other customizations) in docs/README.md. The short version is as follows.

Suppose you want to quickly deploy the service using the following images:

  • gmap/jupyter-isis:8.0.0
  • jupyter/scipy-notebook

You want to guarantee all the images have the same JUPYTERHUB_VERSION installed, this will guarantee hub-notebook fully compatible to each other.

  1. Use docker-compose to build the JupyterHub Docker image:

    docker-compose build
  2. Create the list of image to be used (imagelist):

    echo "gmap/jupyter-isis:8.0.0" > imagelist
    echo "jupyter/scipy-notebook" >> imagelist
  3. Build the Notebook images from given ./imagelist:

    ./setup.sh --build-notebook-images

Now, simply run the service as described in "Run JupyterHub".


/.\

Releases

No releases published

Packages

No packages published

Languages

  • Python 52.0%
  • Shell 26.3%
  • Jinja 11.4%
  • Dockerfile 10.3%