Skip to content

Skopeo should be installed in the github jobs level rather than dockerfile #8242

@javorszky

Description

@javorszky

Version

edge

What Kubernetes platforms are you running on?

Kind

Steps to reproduce

Right now quay skopeo is being tracked in the tests/Dockerfile with a single FROM directive. Skopeo is not used in the tests at all. Its only function is to copy images from Docker to the various registries in copy-images.sh

skopeo has this habit of changing a published version's sha when their base os changes, which means any declared tag:sha pair will become invalid.

Unlike other places, quay seems to remove a tag:sha pair once the sha is updated, which means the older version becomes unavailable and docker pull can't download the image.

Instead we could put the desired docker image version:tag@sha into an environment variable in the GitHub action yaml file and configure renovate to take that into account.

I think renovate's customManagers is a good place to put that config, in case renovate doesn't recognise a docker image string in an env var in a github yaml.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogPull requests/issues that are backlog itemschorePull requests for routine tasksrefinedIssues that are ready to be prioritized

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions