System images reference outdated dependency: docker.io/cockpit/kubernetes:latest

[bit4man]

Attempting to execute the first "introduction to containers" (Linux Container Internals 2.0) the initial pull fails:

Trying to pull registry.access.redhat.com/fedora...
  name unknown: Repo not found
Trying to pull registry.redhat.io/fedora...
  unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication

The guide does not talk about needing to get an account first.

[bit4man]

Followup: It actually does the final failure with:

  toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

So it's not an authentication issue. Wasn't this moved to quay.io?

[ryanj]

I've updated the content to pull from quay.io: https://github.com/openshift-labs/learn-katacoda/commit/518faacd022cac0eb0a3c857d55e0746ee27fbe1

[bit4man]

I've updated the content to pull from quay.io: 518faac

Thanks - that works around the bug. But it does make the initial command the user is exposed to rather complex. Would a better solution be to change /etc/containers/registries.conf to include "registry.fedoraproject.org (perhaps instead of docker.io) that way "podman pull fedora" would still work? Edit: To be sure there's no misunderstanding, the change done works - just confirming this issue seems fixed.

[bit4man]

Same subsystem - part of the OCP 3.11 deployment fails on the last two pages due to the same error: 1h 1h 3 registry-console-1-qtqkx.16684ec9e4521377 Pod spec.containers{registry-console} Normal Pulling kubelet, master pulling image "docker.io/cockpit/kubernetes:latest" 1h 1h 3 registry-console-1-qtqkx.16684ecaa178c170 Pod spec.containers{registry-console} Warning Failed kubelet, master Failed to pull image "docker.io/cockpit/kubernetes:latest": rpc error: code = Unknown desc = toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit 1h 1h 3 registry-console-1-qtqkx.16684ecaa17954a3 Pod spec.containers{registry-console} Warning Failed kubelet, master Error: ErrImagePull

[ryanj]

Looks like /etc/containers/registries.conf is currently configured with:

[registries.search]
registries = ['registry.access.redhat.com', 'registry.redhat.io', 'docker.io']

The docker.io/cockpit/kubernetes:latest image is required by several of our system environments:

$ grep -sr "docker.io/cockpit/kubernetes" .
./environments/openshift-4-5/master/build/3_knative-pull.sh:sudo podman pull docker.io/cockpit/kubernetes
./environments/openshift-4-4/master/build/3_knative-pull.sh:sudo podman pull docker.io/cockpit/kubernetes
./environments/openshift-4-6/master/build/3_knative-pull.sh:sudo podman pull docker.io/cockpit/kubernetes
./environments/openshift-3-10/scripts/knative-pull.sh:docker pull docker.io/cockpit/kubernetes
./environments/openshift-3-11/scripts/7_knative-pull.sh:docker pull docker.io/cockpit/kubernetes

This page seems to indicate that we might be able to pull from registry.access.redhat.com/openshift3/registry-console to fetch a newer image - one that won't be rate-limited by dockerhub: https://catalog.redhat.com/software/containers/openshift3/registry-console/580a32536017d9328b5792da?container-tabs=gti&gti-tabs=unauthenticated