containers/podman

pull --all-tags : confusing documentation

Open

#23,625 opened on Aug 14, 2024

View on GitHub
 (11 comments) (0 reactions) (0 assignees)Go (3,107 forks)batch import
ContribfestGood First Issuedocumentationvolunteers-wanted

Repository metrics

Stars
 (31,686 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

podman pull --all-tags CI test is flaking today due to the quay outage.

Question: is there any way to force --all-tags to respect the aliases in registries.conf?

Issue: docs need improvement because "docker.io" is misleading and wrong and confusing:

IMPORTANT: When using the all-tags flag, Podman does not iterate over the search registries in the containers-registries.conf(5) but always uses docker.io for unqualified image names.

Contributor guide

Research direction
Update the documentation for `podman pull all tags` to clarify that it does not use search registries from registries.conf and always defaults to docker.io for unqualified names. Understand the registries.conf aliases and how all tags currently behaves, then rewrite the relevant section to be accurate and less confusing.
Tech stack
go
Domain
backend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75