Skip to content

docs: clarify when to pull Quay.io image vs build locally #2404

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mathbunnyru merged 3 commits into from
Jan 27, 2026
Merged

docs: clarify when to pull Quay.io image vs build locally #2404

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f0520e8
docs: clarify when to pull Quay.io image vs build locally
CoderLink06 Jan 26, 2026
b4b3190
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] Jan 26, 2026
9805a4b
Fix formatting and capitalization in guidance section
mathbunnyru Jan 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/using/selecting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,19 @@
- [Image Relationships](#image-relationships)
- [Community Stacks](#community-stacks)

> **Pull vs Build: Quick Guidance**
>
> Images are published on **Quay.io** registry and most users should start by pulling an existing image that closely matches their needs.
> Pulling a pre-built image is fast and suitable for common use cases such as running notebooks, teaching, or standard data science workflows.
>
> Building images locally is recommended only when additional customization is required, for example:
>
> - adding system-level packages that cannot be installed at runtime,
> - preinstalling large or complex language-specific libraries,
> - creating organization-specific images or heavy customization for CI.
>
> If unsure, try an existing Quay.io image first; if it falls short, follow the custom images guide to build a tailored image.

Using one of the Jupyter Docker Stacks requires two choices:

1. Which Docker image you wish to use
Expand Down