About Pangeo’s Binder

Much like, the Pangeo’s BinderHub deployment ( allows users to create and share custom computing environments. The main distinction between the two BinderHubs is that Pangeo’s BinderHub allows users to perform scalable computations using the dask-kubernetes package.

For more information on the Pangeo project, check out the online documentation.

Using Pangeo’s Binder

Preparing a repository for use with a BinderHub is quite simple. The best place to start is the BinderHub documentation. The sections below outline some common configurations used on Pangeo’s BinderHub deployment. Specifically, we’ll provide examples of the .dask/config.yaml configuration file and the binder/start script.

Using the Pangeo-Binder Cookiecutter

We have put together a cookiecutter repo to help setup binder repositories that can take advantage of Pangeo. This automates the setup of some of the configuration (described in detail below). The usage for this tool is described below.

pip install -U cookiecutter

After running the cookiecutter command, simply follow the command line instructions to compete setting up your repository. Add some Jupyter Notebooks, configure your environment and push the whole thing to GitHub.

Configuring dask-kubernetes

Dask-kubernetes is a library designed to deploy dask-distributed using Kubernetes. When using dask-kubernetes on binder, you need to specify some basic configuration options. An example of a file named .dask/config.yaml.

# .dask/config.yaml
fuse_subgraphs: False
fuse_ave_width: 0

    bokeh: critical

    link: /user/{JUPYTERHUB_USER}/proxy/{port}/status

      limit: 5s

    max: 50
        dask-worker: True
      restartPolicy: Never
      - args:
          - dask-worker
          - --nthreads
          - '2'
          - --no-bokeh
          - --memory-limit
          - 7GB
          - --death-timeout
          - '60'
        image: ${JUPYTER_IMAGE_SPEC}
        name: dask-worker
            cpu: "1.75"
            memory: 7G
            cpu: 1
            memory: 7G

start script

The start script (e.g. binder/start) provides a mechanism to update the user environment at run time. The start script should look roughly like the example below. A few key points about using the start script:

  • The start script must end with the exec "$@" line.
  • The start script should not do any major work (i.e. don’t download a large dataset using this script)

# Replace DASK_DASHBOARD_URL with the proxy location
sed -i -e "s|DASK_DASHBOARD_URL|/user/${JUPYTERHUB_USER}/proxy/8787|g" binder/jupyterlab-workspace.json
# Get the right workspace ID
sed -i -e "s|WORKSPACE_ID|/user/${JUPYTERHUB_USER}/lab|g" binder/jupyterlab-workspace.json

# Import the workspace into JupyterLab
jupyter lab workspaces import binder/jupyterlab-workspace.json \

exec "$@"

Examples using Pangeo’s Binder