A collection of ready-to-run Docker images containing Jupyter applications and interactive computing tools.
Jupyter Docker Stacks is a collection of ready-to-run Docker images that package Jupyter applications (like JupyterLab and Jupyter Notebook) with pre-installed scientific computing libraries. It solves the problem of environment setup complexity by providing reproducible, containerized environments for data science, machine learning, and interactive computing.
Data scientists, researchers, educators, and developers who need consistent, portable Jupyter environments for analysis, teaching, or prototyping without manual dependency management.
Developers choose Jupyter Docker Stacks for its official, well-maintained images that reduce setup time, ensure compatibility across systems, and offer specialized stacks for different domains (e.g., scipy, datascience) out of the box.
Ready-to-run Docker images containing Jupyter applications
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Includes stacks like scipy-notebook and datascience-notebook with essential libraries pre-installed, reducing setup time for data science projects.
Built for both x86_64 and aarch64 architectures with multi-platform manifests, ensuring broad hardware support, as noted in the CPU Architectures section.
Date-based tags and access to older Ubuntu/Python versions, shown in the table, enable precise environment replication for research.
CUDA-enabled variants for TensorFlow and PyTorch images, available since 2024, facilitate GPU-accelerated machine learning experiments.
Designed to work with JupyterHub for team deployments, mentioned in the quick start examples and documentation.
Migration from Docker Hub to Quay.io requires users to update pull commands, and older Docker Hub images are no longer updated, causing potential workflow disruptions.
Pre-installed scientific packages lead to large Docker images, which can be inefficient for simple use cases or resource-constrained environments.
Extending images with custom Dockerfiles requires deep knowledge of the stack's structure and dependency management, as outlined in the contribution guides.