DirectorySecurity Advisories
Sign In
Directory
jupyterhub-base-notebook logo

jupyterhub-base-notebook

Last changed

Create your Free Account

Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.

Sign Up
Versions
Overview
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Image for jupyterhub-base-notebook

Minimal Jupyter base notebook image using pip

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/jupyterhub-base-notebook:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard registry.

Compatibility Notes

This image is not compatible with the base-notebook image from Jupyter.

The following are the key differences between Chainguard's base-notbook image and the image from Jupyter:

  • The Chainguard Jupyter notebook image ships uses dependencies from PyPI, and does not include conda or mamba.
  • The CMD of the Chainguard image is set to start-notebook.py and passing --ip=0.0.0.0 is required. If you want to use the image with default CMD or use a different CMD, overriding the current CMD is required.
docker run -d -p 8888:8888 cgr.dev/ORGANIZATION/jupyterhub-base-notebook:latest start-notebook.py --ip=x.y.z.a

Getting Started

In order to use Chainguard's Jupyter notebook image, run the following command in your project's directory:

docker run --rm --name=base-notebook -p 8888:8888 -v $(pwd):/home/jovyan cgr.dev/ORGANIZATION/jupyterhub-base-notebook:latest start-notebook.py --ip=0.0.0.0

You will need to retrieve the token from the logs of the container to access the Jupyter notebook. The logs will look like this:

docker logs base-notebook
# truncated
[I 2025-01-02 07:12:43.241 ServerApp] Jupyter Server 2.15.0 is running at:
[I 2025-01-02 07:12:43.241 ServerApp] http://182b5e058be1:8888/lab?token=6901fcbf319446804d212326074998fcf240b34f9429012b
[I 2025-01-02 07:12:43.241 ServerApp]     http://127.0.0.1:8888/lab?token=6901fcbf319446804d212326074998fcf240b34f9429012b

You can then access the Jupyter notebook by visiting the given URL. For example: http://127.0.0.1:8888/lab?token=6901fcbf319446804d212326074998fcf240b34f9429012b.

Documentation and Resources

For more information, please refer to the official documentation for using jupyter notebooks More documentation about image can be found here.

Contact Support

If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.

What are Chainguard Images?

Chainguard Images are a collection of container images designed for security and minimalism.

Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.

The main features of Chainguard Images include:

-dev Variants

As mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev variant which does include a shell and package manager.

Although the -dev image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.

That being said, it’s worth noting that -dev variants of Chainguard Images are completely fine to run in production environments. After all, the -dev variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.

Licenses

Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:

  • Apache-2.0

  • BSD-3-Clause

  • GCC-exception-3.1

  • GPL-2.0-only

  • GPL-2.0-or-later

  • GPL-3.0-or-later

  • LGPL-2.1-or-later

For a complete list of licenses, please refer to this Image's SBOM.

Software license agreement

Category
application

Safe Source for Open Sourceâ„¢
Media KitContact Us
© 2024 Chainguard. All Rights Reserved.
Private PolicyTerms of Use

Product

Chainguard Images