Geek Answers Handbook

Private docker registration status in the Restart (1) section of Forever

I installed the docker private registry using the registry: 2 images in OEL6 using the command below.

docker run -d -p 5000:5000 --restart=always --name bkdevregistry -v /var/lib/docker/certs/:/certs -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/xx.yy.com.crt -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/xx.yy.com.key registry:2

I followed the official guide for creating certificates and setting up the registry.

The system rebooted due to maintenance operations and after the reboot the registry container does not work at all. It immediately goes into Restarting (1) status and does not change its status.

 [ root@slcn09vmf0022 ~]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 44ad9d09d210 registry:2 "/bin/registry /etc/d" 9 minutes ago Restarting (1) 3 minutes ago 0.0.0.0:5000->5000/tcp blkdevreg

Any proposal to bring it to the norm will be appreciated.

Magazine:

 time="2016-05-18T15:29:34Z" level=fatal msg="open : no such file or directory" time="2016-05-18T17:18:47Z" 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.3 instance.id=7034ae26-a1e8-4bc4-828a-be38d17a7ebb version=v2.3.1 time="2016-05-18T17:18:47Z" level=info msg="redis not configured" go.version=go1.5.3 instance.id=7034ae26-a1e8-4bc4-828a-be38d17a7ebb version=v2.3.1 time="2016-05-18T17:18:47Z" level=info msg="Starting upload purge in 51m0s" go.version=go1.5.3 instance.id=7034ae26-a1e8-4bc4-828a-be38d17a7ebb version=v2.3.1 time="2016-05-18T17:18:47Z" level=info msg="using inmemory blob descriptor cache" go.version=go1.5.3 instance.id=7034ae26-a1e8-4bc4-828a-be38d17a7ebb version=v2.3.1
+6
source share
1 answer

try removing the docker registry and restart the docker and iptables service, then restart the docker private registry using the registry: 2, use docker logs to view the error in the log

0
source

More articles:


All Articles