Switch branches/tags
Nothing to show
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
Dockerfile.dashboards Run dashboards server as unpriv user May 12, 2016
Dockerfile.kernel Bump to notebook 4.2 May 28, 2016
README.md Add public redirect link to db_secrets Jul 25, 2016
docker-compose.yml Bump declarative widgets version in docker and dev deployments. Oct 4, 2016
nb_secrets.env Move secrets to env_files Jun 26, 2016


This folder contains a recipe for deploying a dashboard server, kernel gateway server, and notebook server to a Docker host. Consider this a starting point that needs tuning to your particular environment. See the sibling cf_deploy folder for an alternative using Cloud Foundry.


  • Docker Compose 1.6.0+
  • Docker Engine 1.10.0+
  • Docker Machine 0.6.0+ (or suitable docker environment)

Try It

eval $(docker-machine env your_host)

# add --no-cache --force-rm if switching versions
docker-compose build

# modify the passwords, redirect URLs, etc. in
# nb_secrets.env and db_secrets.env to fit your environment

docker-compose up

After running the above, open a browser to http://<your docker host IP>:8888 to access the notebook server. Open the hello world notebook, run it, switch to dashboard mode to see it working. Then use the File → Deploy As → Dashboard on Jupyter Dashboard Server. After deploying, the notebook server will automatically redirect you to the dashboard server running on http://<your docker host IP>:3000. Login with demo as the username and password.

If you want to run the meetup-streaming notebook on the dashboard server, make sure you run them first in the notebook server so that all of the declarative widgets are available for deployment.

If you want to customize the secrets used in the deployment, make changes to the nb_secrets.env and db_secrets.env files. Keep in mind that storing secrets in environment files may not be appropriate for your use case.

See It

Notebook to dashboard screencast