I’m trying to set up my private Docker Registry and I’m following the official documentation.
I have installed Docker and I’m able to run my registry on my server. But I want my registry to be more widely available.
My docker-server with the private registry is installed on an AWS-instance.
I am also getting similar error when trying to push docker images to registry. The registry hangs for sometime with the same error and after trying to push multiple times, push gets successful. Is it something to do with registry version? Any suggestions to replicate the errors or overcome these errors is highly appreciated
unable to ping registry endpoint https://ec2-xx-xx-xx-xx.compute.amazonaws.com:5000/v0/
v2 ping attempt failed with error: Get https://ec2-xx-xx-xx-xx.compute.amazonaws.com:5000/v2/: dial tcp 10.0.x.x:5000: no route to host
v1 ping attempt failed with error: Get https://ec2-xx-xx-xx-xx.compute.amazonaws.com:5000/v1/_ping: dial tcp 10.0.x.x:5000: no route to host
Thanks, this was already a great help. The permission error is gone.
Can I really choose the name my.registry.common.name or do I have to use the name of my EC2 instance: ec2-xx-xx-xx-xx.us-xxx-1.compute.amazonaws.com
time=“2015-12-14T07:43:23Z” level=warning msg=“No HTTP secret provided - generated random secret. This may cause problems with uploads if multiple registries are behind a load-balancer. To provide a shared secret, fill in http.secret in the configuration file or set the REGISTRY_HTTP_SECRET environment variable.” go.version=go1.5.2 instance.id=85b9c6ec-5e74-47d6-ad52-784c59bb7d1c version=v2.2.1
time=“2015-12-14T07:43:23Z” level=info msg=“redis not configured” go.version=go1.5.2 instance.id=85b9c6ec-5e74-47d6-ad52-784c59bb7d1c version=v2.2.1
time=“2015-12-14T07:43:23Z” level=info msg=“using inmemory blob descriptor cache” go.version=go1.5.2 instance.id=85b9c6ec-5e74-47d6-ad52-784c59bb7d1c version=v2.2.1
time=“2015-12-14T07:43:23Z” level=info msg=“Starting upload purge in 56m0s” go.version=go1.5.2 instance.id=85b9c6ec-5e74-47d6-ad52-784c59bb7d1c version=v2.2.1
time=“2015-12-14T07:43:23Z” level=info msg=“listening on [::]:5000, tls” go.version=go1.5.2 instance.id=85b9c6ec-5e74-47d6-ad52-784c59bb7d1c version=v2.2.1
Edit the /etc/hosts and add 10.0.0.X private-registry (my internap IP and the name of my registry)
Copied my domain.crt to /etc/docker/cert.d/private-registry:5000/domain.crt
Error:
The push refers to a repository [private-registry:5000/ubuntu] (len: 1)
unable to ping registry endpoint https://private-registry:5000/v0/
v2 ping attempt failed with error: Get https://private-registry:5000/v2/: net/http: TLS handshake timeout
v1 ping attempt failed with error: Get https://private-registry:5000/v1/_ping: net/http: TLS handshake timeout
I have a registry wich is using selfsigned certificates. OpenShift will
create images for my s2i-projects and those will be stored in the
OpenShift Docker Registry. From there I want to push them manually to my
own registry (which is using selfsigned certificates).
The logs of my registry
time=“2015-12-15T13:44:05Z”
level=warning msg=“No HTTP secret provided - generated random secret.
This may cause problems with uploads if multiple registries are behind a
load-balancer. To provide a shared secret, fill in http.secret in the
configuration file or set the REGISTRY_HTTP_SECRET environment
variable.” go.version=go1.5.2
instance.id=a785b46c-6eac-4fff-9d78-0774abd46a8c version=v2.2.1
time=“2015-12-15T13:44:05Z”
level=info msg=“redis not configured” go.version=go1.5.2
instance.id=a785b46c-6eac-4fff-9d78-0774abd46a8c version=v2.2.1
time=“2015-12-15T13:44:05Z”
level=info msg=“using inmemory blob descriptor cache”
go.version=go1.5.2 instance.id=a785b46c-6eac-4fff-9d78-0774abd46a8c
version=v2.2.1
time=“2015-12-15T13:44:05Z”
level=info msg=“Starting upload purge in 55m0s” go.version=go1.5.2
instance.id=a785b46c-6eac-4fff-9d78-0774abd46a8c version=v2.2.1
time=“2015-12-15T13:44:05Z”
level=info msg=“listening on [::]:5000, tls” go.version=go1.5.2
instance.id=a785b46c-6eac-4fff-9d78-0774abd46a8c version=v2.2.1
2015/12/15 13:44:34 http: TLS handshake error from 10.0.0.xx:43442: EOF
2015/12/15 13:44:39 http: TLS handshake error from 10.0.0.xx:43443: EOF
2015/12/15 13:44:49 http: TLS handshake error from 10.0.0.xx:43460: EOF
2015/12/15 13:45:25 http: TLS handshake error from 10.0.0.xx:43479: tls: first record does not look like a TLS handshake
2015/12/15 13:45:58 http: TLS handshake error from 10.0.0.xx:43488: EOF
2015/12/15 13:46:03 http: TLS handshake error from 10.0.0.xx:43491: EOF
2015/12/15 13:46:13 http: TLS handshake error from 10.0.0.xx43496: EOF
hi friend.
you install the registry which is provied by docker. It is not use ssl. So you should disable the ssl in the client host.
if your client host’s env is centos7.
you should modity the file "/usr/lib/systemd/system/docker.service"
add the option “–insecure-registry=[registry-host]:5000” to disable the ssl between client host and registry host.
So a key thing when you are using Docker registry instance in AWS with an ELB in front of registry server, make sure your ELB Idle Timeout setting is at maximum value if you have several large layers of image to be pushed to registry server. Default value is 60 sec and max possible is 3600 sec.
i have same confusion with all, only but similar error with “https://***:5000/v1/_ping : forbidden port” came with my case. now yet there is no any valid solution