From 18a0ef02dcf066c499cdcd39bf06088c037b2058 Mon Sep 17 00:00:00 2001 From: Jannik Date: Mon, 9 Nov 2020 21:35:38 +0100 Subject: [PATCH] Typo in the code ticks markdown --- Running-with-systemd-docker.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Running-with-systemd-docker.md b/Running-with-systemd-docker.md index a2b0898..a402bd4 100644 --- a/Running-with-systemd-docker.md +++ b/Running-with-systemd-docker.md @@ -41,7 +41,7 @@ Explanation of options which may not be self-explanatory: - A `TimeoutStartSec` value of 0 stops systemd from considering the service failed after waiting for the default startup time. This is required as it may take a while for the `docker pull` in `ExecStartPre` to finish. - `ExecStartPre`: Pull the docker tag before running. -- `ExecStopPost`: Delete the container (to make sure we can start again next time). The reason we do that is because systemd is monitoring the docker service instead of the individual container. As such we tell the docker service to restart the container `unless-stopped. That is basically like `--restart=Always`, but excluding when the docker service stopped (or the container was halted). This allows us to only restart the service `Restart=Always` with systemd when the docker service stopped. +- `ExecStopPost`: Delete the container (to make sure we can start again next time). The reason we do that is because systemd is monitoring the docker service instead of the individual container. As such we tell the docker service to restart the container `unless-stopped`. That is basically like `--restart=Always`, but excluding when the docker service stopped (or the container was halted). This allows us to only restart the service `Restart=Always` with systemd when the docker service stopped. - A `Type` value of `notify` tells systemd to expect a notification from the service that it is ready. - A `NotifyAccess` value of `all` is required by `systemd-docker`.