Replies: 2 comments
-
@mtrmac PTAL |
Beta Was this translation helpful? Give feedback.
-
I don’t understand the problem. Steps to reproduce / expected results / actual results? If the registry tag points at and image with an amd64 digest of sha256:9af4ed962405e24b37240ce34a2272e40cff99b4f5150cc6a53b03f95d40e6e0 and the pulled image has an amd64 digest sha256:9af4ed962405e24b37240ce34a2272e40cff99b4f5150cc6a53b03f95d40e6e0 , AFAICT Podman’s job is done and whatever is or isn’t inside the image is between the producer and consumer. Or is the claim that the pulled image is not actually sha256:9af4ed962405e24b37240ce34a2272e40cff99b4f5150cc6a53b03f95d40e6e0 ? There isn’t any reason in general to expect that the time an image was built and the time the image was published should match. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I'm new to podman so if it's intended behavior please let me know.
I'm trying to create a Rust dev container. Currently the latest Rust version is 1.75.0, in my Dockerfile I tried both
docker.io/rust:1-alpine
anddocker.io/rust:1.75-alpine
(they are the same version), in both case, podman pulls an image with rustc version of 1.72.1. On docker hub, the latest image is shown as been created 6 days ago, the one pulled to my machine was created 5 weeks ago. However,podman inspect
shows correct repo digest. What could be wrong?Beta Was this translation helpful? Give feedback.
All reactions