Harbor use, use private mirror library to do mirror ▫ 405 78 error

Problem Description:
Set up a good harbor after the use of the local mirror library to do harbor mirror, docker configuration ExecStart = / usr / bin / docker daemon -H fd: // -D –registry-mirror = –insecure- Registry
If you do not consider harbor, a separate push image can push to a private mirror library. If added to harbor's harbor / Deploy / config / registry / config.yml
Remoteurl: https://registry-1.docker.io

Command line login harbor, to the corresponding account in the corresponding project push mirror harbor reported

  • Openshift use registry and router
  • [Help] private registry mirror has a layer to push the problem
  • How to manage Docker regisrtry permissions
  • Docker private library management
  • Registry V1 upgrade to V2
  • Docker registry ui interface, harbor and portus which is good
  • Error "auth.user.name = xxx err.code = unsupported err.message =" The operation is unsupported
    HTTP / 1.1 "405 78" "" 2016-05-10 add comment share it

    • Weibo
    • QZONE
    • Micro letter

    Did not find the relevant results


      Bean bag

      We agreed from:

      Remoteurl: https://registry-1.docker.io
      Should be him, and get rid of it

    • Private warehouse push image prompt failed to upload metadata ... docker-registry: no such host
    • How to build a safe and reliable Docker Registry?
    • [Original] an enhanced version of the docker registry
    • What are the private registry solutions for everyone?
    • The Docker Beta version of Windows
    • VMware Harbor: Enterprise-based Registry services based on Docker Distribution
    • Heads up! This alert needs your attention, but it's not super important.