Skip to content
Snippets Groups Projects
Commit a457e689 authored by Anand Patil's avatar Anand Patil
Browse files

Added section to README about detaching client

parent faf1c44d
No related branches found
No related tags found
No related merge requests found
......@@ -100,6 +100,11 @@ By default `systemd-docker` will send READY=1 to the systemd notification socket
What this will do is set up a bind mount for the notification socket and then set the NOTIFY_SOCKET environment variable. If you are going to use this feature of systemd, take some time to understand the quirks of it. More info in this [mailing list thread](http://comments.gmane.org/gmane.comp.sysutils.systemd.devel/18649). In short, systemd-notify is not reliable because often the child dies before systemd has time to determine which cgroup it is a member of
Detaching the client
====================
The `-d` argument to docker has no effect under `systemd-docker`. To cause the `systemd-docker` client to detach after the container is running, simply use `--logs=false --rm=false`. If either `--logs` or `--rm` is true, the `systemd-docker` client will stay alive until it is killed or the container exits.
Running on CoreOS
=================
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment