Kubernetes Private Docker Registry Push Error

So I have deployed a Kubernetes cluster and installed a private Docker registry. Here is my registry controller:

  apiVersion: v1
  kind: ReplicationController
    name: registry-master
      name: registry-master
    replicas: 1
      name: registry-master
          name: registry-master
        - name: registry-master
          image: registry
          - containerPort: 5000
          command: ["docker-registry"]

And the service:

  • Docker Registry and Basic Auth
  • Install PHP 7 extensions in docker container
  • What is the difference between running software in a Docker container Vs Real OS
  • Error reading webpack-stats.json
  • Dynamically change dockerrun.aws.json image tag on deploy
  • How do I get host networking to work with docker swarm mode
  • ---
      apiVersion: v1
      kind: Service
        name: registry-master
          name: registry-master
          # the port that this service should serve on
        - port: 5000
          targetPort: 5000
          name: registry-master

    Now I sshed to one of Kubernetes’ nodes and built a Ruby app container:

    cd /tmp
    git clone https://github.com/RichardKnop/sinatra-redis-blog.git
    cd sinatra-redis-blog
    docker build -t ruby-redis-app

    When I try to tag it and push it to the registry:

    docker tag ruby-redis-app registry-master/ruby-redis-app
    docker push

    I am getting this error:

    Error response from daemon: invalid registry endpoint unable to ping registry endpoint
    v2 ping attempt failed with error: Get read tcp connection reset by peer
     v1 ping attempt failed with error: Get read tcp connection reset by peer. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/

    Any idea how to solve it? I have been struggling with this for several hours.


  • ClassNotFoundException when submitting yamr job to remote cluster
  • Use of docker tomcat with external WAR
  • Docker swarm on AWS - swarm services cannot access internet
  • connecting Docker to a cloud provider, Amazon AWS
  • unable to start docker after upgrading to 1.12 version
  • Is it possible to allow docker use the host machines dnses?
  • 3 Solutions collect form web for “Kubernetes Private Docker Registry Push Error”

    if you’re using HTTPS, you must have created a self-signed certificate (with your own CA authority) or you have a CA signed certificate.

    If so, you need to install this CA cert on the machine you’re calling FROM

    put your CA cert in


    and run


    sometimes I have had to put it also in


    (in both cases your CA file EXTENSION should be .pem

    For Docker you may also need to put a file in


    and the file must be named ca.crt
    (same file file as the .pem file but named ca.crt)

    I saw a similar issue and it was related to my registry not supporting https. If your registry does not support https, then you’ll have to specify it’s an insecure registry to the docker daemon

    echo ‘DOCKER_OPTS=”–insecure-registry″‘ | sudo tee -a /etc/default/docker

    And then restart your docker daemon.

    If you are using Ubuntu, add this line into your /etc/default/docker file.

    $DOCKER_OPTS=“--insecure-registry xxx.xxx.xxx.xxx:5000”

    Where the xxx.xxx.xxx.xxx is your private registry ip.

    And then restart your docker client.

    sudo docker service restart
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.