While looking into consuming container images from other-than-docker-hub repositories, it seems that https://registry.centos.org/ gives http-error 502. This prevents using the centos:latest container references from being replaced with their location on the CentOS Container Registry.
centos:latest
If the registry is expected to be stable, please let me know so that I can update our tests.
Even though the website is offline, it seems pulling images is not affected. The following just works fine:
$ podman pull registry.centos.org/centos:latest Trying to pull registry.centos.org/centos:latest... Getting image source signatures Copying blob c721dabf6e34 done Copying config b7b1daa78b done Writing manifest to image destination Storing signatures b7b1daa78b4442db3e016f27e235c9d895c675e3e72562191892dd8ea6b8ddb9
Sorry, closing as registry.centos.org is not managed by CentOS Infra. You can directly reach out to @bamachrn but I'll close this request
CentOS doesn't even push/use that registry and official images are pushed to Dockerhub (see https://www.centos.org/download/#cloud-and-container-images and so link to https://registry.hub.docker.com/_/centos/)
Metadata Update from @arrfab: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.