Docker registry takes extended time to restart after a system reboot

[sathsarasa]

Docker version 1.12.6, build d5236f0

There was a system reboot after a coreos upgrade in the private docker registry node.

It took more than 12 hours to start the docker registry after this reboot.

We recreated this issue 3 times by rebooting the system. Below are the time periods taken to start the docker registry.

• Attempt 1 - 10 minutes
• Attempt 2 - 30 minutes
• Attempt 3 - 50 minutes

However, we observed that docker container is getting started immediately when we list docker processes with 'docker ps' command. This was observed twice after manually rebooting the system.

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                  PORTS                    NAMES
d56174472283        registry:2.3.1      "/bin/registry /etc/d"   9 days ago          Up Less than a second   0.0.0.0:5000->5000/tcp   registry
898bd33c8ce0        cloudwatch:v3       "/usr/local/bin/run.s"   13 days ago         Up Less than a second   0.0.0.0:9090->9090/tcp   small_mccarthy