Browse Source

systemd: set service type to notify.

Currently the service type is 'simple', the default, meaning that
docker.service is considered to be started straight after
spawning. This is incorrect as there is significant amount of time
between spawning and docker ready to accept connections on the passed
sockets. Docker does implement systemd socket activate and
notification protocol, and send the ready signal to systemd, once it
is ready. However for systemd to take those notifications into
account, the service file type should be set to notify.

Signed-off-by: Dimitri John Ledkov <dimitri.j.ledkov@intel.com>
Dimitri John Ledkov 10 years ago
parent
commit
d3e5179c29
1 changed files with 1 additions and 0 deletions
  1. 1 0
      contrib/init/systemd/docker.service

+ 1 - 0
contrib/init/systemd/docker.service

@@ -5,6 +5,7 @@ After=network.target docker.socket
 Requires=docker.socket
 Requires=docker.socket
 
 
 [Service]
 [Service]
+Type=notify
 ExecStart=/usr/bin/docker daemon -H fd://
 ExecStart=/usr/bin/docker daemon -H fd://
 MountFlags=slave
 MountFlags=slave
 LimitNOFILE=1048576
 LimitNOFILE=1048576