Skip to content

make pull-policy=newer finally working #28997

Description

@hadmut

Feature request description

Hi,
several podman commands such as run and build have a parameter --pull-policy, where the man pages tell

   • newer: Pull if the image on the registry is newer than the one in the local containers storage.  An image is considered to be newer when the digests are different.  Comparing the time stamps is prone to errors.  Pull errors are suppressed if a local image was found.

Thousands of other program cans properly compare times stamps.

why the hell shouldn't podman be able to compare timestamps? That's standard function of runtime libraries, and it is just ridiculous to deny beeing able to do that.

And I had to struggle with severe problems when podman replaced freshly built images with older ones.

If you really need that, keep it as pull-policy=different, but do make pull-policy=newer working what it means, i.e. pull only newer images.

It is not rocket science to compare two dates.

Suggest potential solution

A clear and concise description of what you want to happen.

Have you considered any alternatives?

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions