-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-9.6
-
rhel-sst-container-tools
-
5
-
False
-
-
None
-
RUN 262, RUN 263, RUN 265, RUN 266, RUN 267
-
Requested
-
None
-
-
All
-
None
What were you trying to do that didn't work?
When using any tool using the containers/image and containers/storage libraries (Podman, Buildah) and pulling a zstd:chunked image from a registry with partial pull support enabled, image IDs may not be consistent between different systems if some layers of the image already exist and were not pulled as zstd:chunked layers (e.g. they were loaded via `podman load` instead of pulled). This constitutes a breaking change if it is not fixed.
What is the impact of this issue to you?
Scripts and tests relying on consistent image IDs are broken. Imports of checkpoints are broken.
Please provide the package NVR for which the bug is seen:
Any existing Podman binary
How reproducible is this bug?:
100%
Steps to reproduce
- Choose a base image and export it with `podman save`
- Build an image with that base image, adding at least one layer (e.g. ADD instruction)
- Push the built image to a registry using zstd:chunked compression
- On one system, import the image saved with `podman save` then pull the image that was built.
- On another system, pull the image from the registry without importing
Expected results
Image IDs for the built image are the same on both systems
Actual results
Image IDs for the built image differ on the two systems
- is depended on by
-
OCPSTRAT-1285 Speeding Up Pulling Container Images
-
- Backlog
-
- relates to
-
RUN-2311 zstd:chunked Delivery
-
- In Progress
-
- links to
-
RHSA-2024:139679 podman security, bug fix and enhancement update