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 popular data science and machine learning libraries. It solves the problem of environment setup and dependency management by providing pre-configured, reproducible containers for interactive computing.
Data scientists, researchers, educators, and developers who need consistent, portable Jupyter environments for data analysis, machine learning, or scientific computing workflows.
Developers choose Jupyter Docker Stacks because it eliminates environment configuration headaches, ensures reproducibility across teams and deployments, and offers a wide variety of specialized stacks (e.g., with TensorFlow, PyTorch, or R) 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 domain-specific images like scipy-notebook and datascience-notebook with essential libraries pre-installed, eliminating manual setup for data science workflows.
Builds for both x86_64 and aarch64 with multi-platform manifests, ensuring compatibility across Intel/AMD and Apple Silicon hardware, as noted in the CPU Architectures section.
Offers date-based tags and access to older Ubuntu/Python versions via specific hashes, facilitating reproducible research and experiment tracking.
Provides CUDA-enabled variants for PyTorch and TensorFlow images, streamlining machine learning workloads on NVIDIA GPUs without manual configuration.
Since 2023-10-20, images are only on Quay.io with Docker Hub deprecated, forcing users to update pull commands and potentially breaking existing CI/CD pipelines.
Changing defaults like the Jupyter frontend or root directory requires passing environment variables or command-line arguments, adding steps for simple tweaks, as shown in the 'Choosing Jupyter frontend' note.
Stacks include numerous libraries by default, resulting in large Docker images that may be inefficient for resource-constrained environments or users needing only a subset of tools.