Default Cache Reuse vs Forced Refresh: Addressing Stale Image Results in Podman
In current Podman releases, the default pull behavior reuses locally stored image layers and manifests, only downloading new data when the registry manifest digest changes. When a registry image is retagged without altering its digest, the local cache may serve stale content that does not reflect the intended registry state. This creates a design tension: re
podman