Turn git repositories into Jupyter-enabled Docker Images
 
 
 
 
 
 
Go to file
tdalseide 1348829fd0 Moved old COPYING.md to LICENSE, and updated with current language. 2017-08-26 20:30:15 +02:00
docs config file for RTD 2017-08-01 13:20:50 -04:00
repo2docker Add npm to base image 2017-08-01 23:18:15 -07:00
tests updating autogen examples 2017-08-01 11:21:06 -04:00
.dockerignore Update gitignore + add dockerignore 2017-05-09 20:43:27 -07:00
.gitignore fixing RTD build 2017-08-01 13:11:06 -04:00
.travis.yml Print stdout for all the tests! 2017-07-30 02:44:12 -07:00
Dockerfile Cleanup Dockerfile + Manifest 2017-07-29 16:49:40 -07:00
LICENSE Moved old COPYING.md to LICENSE, and updated with current language. 2017-08-26 20:30:15 +02:00
MANIFEST.in Include package_data in setup.py 2017-08-02 01:29:50 -07:00
Makefile Add makefile for building and pushing image 2017-05-28 19:25:56 -07:00
README.md Add a little more info to README 2017-07-30 03:08:26 -07:00
readthedocs.yml config file for RTD 2017-08-01 13:20:50 -04:00
setup.cfg apply platform tag to wheels 2017-05-24 10:01:24 -07:00
setup.py Include package_data in setup.py 2017-08-02 01:29:50 -07:00

README.md

jupyter-repo2docker

Build Status

jupyter-repo2docker is a tool to build, run and push docker images from source code repositories.

Pre-requisites

  1. Docker to build & run the repositories. The community edition is recommended.
  2. Python 3.4+.

Installation

To install from pypi, the python packaging index:

pip install jupyter-repo2docker

To install from source:

git clone https://github.com/jupyter/repo2docker.git
cd repo2docker
pip install .

Usage

The core feature of repo2docker is to fetch a repo (from github or locally), build a container image based on the specifications found in the repo & optionally launch a local Jupyter Notebook you can use to explore it.

Example:

jupyter-repo2docker https://github.com/jakevdp/PythonDataScienceHandbook

After building (it might take a while!), it should output in your terminal something like:

    Copy/paste this URL into your browser when you connect for the first time,
    to login with a token:
        http://0.0.0.0:36511/?token=f94f8fabb92e22f5bfab116c382b4707fc2cade56ad1ace0

If you copy paste that URL into your browser you will see a Jupyter Notebook with the contents of the repository you had just built!

Repository specifications

Repo2Docker looks for various files in the repository being built to figure out how to build it. It is philosophically similar to Heroku Build Packs.

It currently looks for the following files. They are all composable - you can use any number of them in the same repository (except for Dockerfiles, which take precedence over everything else).

requirements.txt

This specifies a list of python packages that would be installed in a virtualenv (or conda environment).

environment.yml

This is a conda environment specification, that lets you install packages with conda. Note that you must leave the name of the environment empty for this to work out of the box.

apt.txt

A list of debian packages that should be installed. The base image used is usually the latest released version of Ubuntu (currently Zesty.)

postBuild

A script that can contain arbitrary commands to be run after the whole repository has been built. If you want this to be a shell script, make sure the first line is #!/bin/bash. This file must have the executable bit set (chmod +x postBuild) to be considered.

REQUIRE

This specifies a list of Julia packages! Currently only version 0.6 of Julia is supported, but more will be as they are released.

Dockerfile

This will be treated as a regular Dockerfile and a regular Docker build will be performed. The presence of a Dockerfile will cause all other building behavior to not be triggered.