Push Against Secure, Exposed Registry Fails with Authentication Messages

Solution Verified - Updated -

Issue

  • We have exposed the registry and since upgrading to 3.5 have been unable to push to it.
  • Authenticating to the registry works fine however when we go to push we get the following:
# docker login -u example -p registry.openshift.example.com
Login Succeeded
# docker push registry.openshift.example.com/openshift/php:latest
Cannot set persistent booleans, please try as root.
The push refers to a repository [registry.openshift.example.com/openshift/php]
95c4fd550d8e: Preparing
b41b282bd373: Preparing
3cb03dc081c0: Preparing
f483edd7a42b: Preparing
f7b626558f10: Preparing
unauthorized: authentication required
  • Pushing to the internal IP works just fine, its just the exposed part that is failing to work since upgrade.
Jun 12 11:36:23 node1.openshift.example.com dockerd-current[20638]: time="2017-06-12T11:36:23.893714348-04:00" level=error msg="Upload failed: unauthorized: authentication required"
Jun 12 11:36:23 node1.openshift.example.com dockerd-current[20638]: time="2017-06-12T11:36:23.894356675-04:00" level=error msg="Attempting next endpoint for push after error: unauthorized: authentication required"

Environment

  • Red Hat OpenShift Container Platform
    • 3.5
    • 3.6
  • OpenShift Online v3

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