docs: clarify --all-tags and --include-volumes behavior

Unqualified names with --all-tags always resolve via docker.io rather
than registries.conf search lists. Spell that out, and note that
--include-volumes only applies when set to true.

Fixes #23625
Fixes #15387

Signed-off-by: Dean Chen <862469039@qq.com>
This commit is contained in:
Dean Chen 2026-07-30 18:39:50 +05:00 • committed by Paul Holzinger
parent 7ca6c0e94c
commit bce0a59c3c
No known key found for this signature in database
GPG key ID: EB145DD938A3CAF2
2 changed files with 6 additions and 2 deletions

View file

@ -10,4 +10,8 @@
All tagged images in the repository are pulled.
*IMPORTANT: When using the all-tags flag, Podman does not iterate over the search registries in the **[containers-registries.conf(5)](https://github.com/containers/image/blob/main/docs/containers-registries.conf.5.md)** but always uses docker.io for unqualified image names.*
*IMPORTANT: With **--all-tags**, Podman does **not** walk the unqualified-search registries from
**[containers-registries.conf(5)](https://github.com/containers/image/blob/main/docs/containers-registries.conf.5.md)**
for short (unqualified) names. Unqualified names are resolved as if they lived on **docker.io**
(for example `alpine` becomes `docker.io/library/alpine`). To pull every tag from another registry,
use a fully qualified image name such as `quay.io/myorg/myimage` or `registry.example.com/ns/name`.*

View file

@ -55,7 +55,7 @@ Write the image ID to the file.
#### **--include-volumes**
Include in the committed image any volumes added to the container by the **--volume** or **--mount** OPTIONS to the **[podman create](podman-create.1.md)** and **[podman run](podman-run.1.md)** commands.\
The default is **false**.
This only takes effect when set to **true**. The default is **false** (volume contents are not copied into the image).
#### **--message**, **-m**=*message*