Skip to content

quay.io in registries.conf can yield misleading errors #301

@harmathy

Description

@harmathy

The current containers registries.conf (installed as /etc/containers/registries.conf.d/crio.conf) leads in combination with the docker hub rate-limit to hard to interpret error messages.

The content of the configuration:

unqualified-search-registries = ["docker.io", "quay.io"]

will for example resolve an image debian:stable first to docker.io/debian:stable (which then again gets normalized to docker.io/library/debian:stable by the containers libs) and second to quay.io/debian:stable which simply does not exist.

Therefore a fully qualified container image which can't be pulled due to the rate-limit will yield an error message giving hints about the actual cause to the operator:

Failed to pull image "docker.io/library/debian:stable": initializing source
docker://debian:stable: reading manifest stable in docker.io/library/debian:
toomanyrequests: You have reached your unauthenticated pull rate limit.
https://www.docker.com/increase-rate-limit

With an unqualified container image the error message can be quite misleading:

Failed to pull image "debian:stable": initializing source
docker://quay.io/debian:stable: reading manifest stable in quay.io/debian:
StatusCode: 404, "<!doctype html>\n<html lang=en>\n<title>404 Not Foun..."

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions