Closed rhatdan closed 3 months ago
This seems like a pretty significant breaking change.
Only think different from my understanding is that always will attempt to pull even if the image exists in local storage, which is very wrong. where as newer will pull only if the image in the registry is different then the local one.
Hard to see how this could break anyone. @nalind @mtrmac Does --pull always actually replace the content in containers storage with the same content again, or does it pull and then realize it already has the content and drop it.
Oops my mistake, went from pull=missing to pull=newer to match Docker defaults to missing, reverting that change
An image is considered to be newer when the digests are different.
Per that, the newer
is a just a lie.
I don’t immediately know what the options do in detail… it’s up to the author of the PR to understand the situation and advocate for a specific change.
c/image would typically not re-pull layers already present locally. For the most part, “pulling exactly the image again” should be a cheap enough mostly-metadata operation, such that “optimizing that out” by making another check should, ideally, not make things faster. In practice, there are complications.
So, I think the difference between newer
and always
is basically these complications.
@containers/podman-maintainers PTAL
This is now pretty much just a documentation change. PTAL.
@giuseppe @nalind @mheon @mtrmac @flouthoc @baude @Luap99 PTAL
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: flouthoc, rhatdan, vrothberg
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Just for simplification of the code.
Does this PR introduce a user-facing change?