Red Hat Bugzilla – Bug 1286765
docker should not time out on sd_notify
Last modified: 2016-03-31 19:23:02 EDT
+++ This bug was initially created as a clone of Bug #1286763 +++
We have found several situations where docker takes a long time to start. When running in the cloud for example, docker on initial start takes a long time to created the storage on devicemapper/loopback, this is blowing up in certain situations.
When we move to docker 1.10, docker will rewrite the image labels UUID based on content in the images, this could take a huge amount of time, and should not be killed by systemd.
We need to set the timeout to 0 to allow docker all the time it needs to startup.
Fixed in docker-1.10
In docker-1.9.1-23.el7.x86_64, the parameter in docker.service has been added with 0, TimeoutStartSec=0
move to verified
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.