Mirror registry fails in disconnected environment with missing or incorrect pause image

Solution Verified - Updated -

Issue

TASK [mirror_appliance : Starting Pod with ports 80 and 443 exposed] *******************************************************************
fatal: [root@localhost]: FAILED! => {"changed": false, "msg": "Can't create pod quay-pod", "stderr": "time=\"2022-02-16T12:15:41Z\" level=warning msg=\"failed, retrying in 1s ... (1/3). Error: initializing source docker://k8s.gcr.io/pause:3.5: pinging container registry k8s.gcr.io: Get \\\"http://k8s.gcr.io/v2/\\\": dial tcp 127.0.0.1:80: connect: connection refused\"\ntime=\"2022-02-16T12:15:42Z\" level=warning msg=\"failed, retrying in 1s ... (2/3). Error: initializing source docker://k8s.gcr.io/pause:3.5: pinging container registry k8s.gcr.io: Get \\\"http://k8s.gcr.io/v2/\\\": dial tcp 127.0.0.1:80: connect: connection refused

Environment

  • Red Hat Quay
    • 3.6
  • Mirror Registry
    • 1.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content