jupyter/docker-stacks

Ready-to-run Docker images containing Jupyter applications

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 28 minutes ago
Added to GitGenius on September 7th, 2026
Created on July 15th, 2015
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 2,981
Total Stargazers: 8,463 (+0)
Total Subscribers: 181 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.8 hours
Mean response time: 18.0 days
90th percentile: 23.1 days
Tracked items: 65

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 11% of issues opened in the past year have been closed. Three people close 79% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Jupyter Docker Stacks is a collection of ready-to-run Docker images that contain Jupyter applications and interactive computing tools.

The project solves the problem of setting up Jupyter environments by providing pre-configured Docker images that eliminate the need to manually install and configure Jupyter, Python, and related dependencies. Users can pull an image and immediately run a Jupyter Server with either JupyterLab or Jupyter Notebook frontend, or use the images as a base for custom project Dockerfiles. The stacks are organized hierarchically, allowing developers to choose images matched to their use case, whether running a personal server, deploying JupyterHub for teams, or building specialized environments.

The tool suits individual developers wanting to quickly spin up isolated Jupyter environments, teams deploying shared JupyterHub instances, and anyone building Docker-based projects that need Jupyter as a foundation. The images can be run as persistent containers that survive restarts or as ephemeral containers that clean up automatically while preserving mounted host directories. Developers should choose this approach when they want to avoid dependency management overhead and prefer containerized, reproducible computing environments.

The project maintains multiple image variants published to a container registry, with documentation on ReadTheDocs covering image selection and usage patterns. Development activity shows ongoing maintenance of the image build infrastructure and regular updates to keep dependencies current.