From a463ff657c226ab1af12befc0ded1ff0bd75e63d Mon Sep 17 00:00:00 2001 From: Andreas Runfalk Date: Fri, 31 Jul 2020 15:24:29 +0200 Subject: [PATCH] Fixed some problems with the "New container every restart" chapter --- Using-Podman.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Using-Podman.md b/Using-Podman.md index 3bbefc4..56e5d6b 100644 --- a/Using-Podman.md +++ b/Using-Podman.md @@ -35,8 +35,8 @@ If we want to create a new container every time the service starts we can edit t [Service] Restart=on-failure ExecStartPre=/usr/bin/rm -f /%t/%n-pid /%t/%n-cid -ExecStart=/usr/bin/podman run --conmon-pidfile /%t/%n-pid --env-file=/home/spytec/Bitwarden/bitwarden.conf -d -p 8080:8080 -v /home/spytec/Bitwarden/bw-data:/data/:Z bitwardenrs/server:latest -ExecStop=/usr/bin/podman rm -f --cid-file /%t/%n-cid +ExecStart=/usr/bin/podman run --conmon-pidfile /%t/%n-pid --cidfile /%t/%n-pid --env-file=/home/spytec/Bitwarden/bitwarden.conf -d -p 8080:8080 -v /home/spytec/Bitwarden/bw-data:/data/:Z bitwardenrs/server:latest +ExecStop=/usr/bin/podman rm -f --cidfile /%t/%n-cid KillMode=none Type=forking PIDFile=/%t/%n-pid @@ -46,7 +46,7 @@ Where `bitwarden.conf` environment file can contain all the container environmen ROCKET_PORT=8080 ``` -If you want the container to have a specific name, you might need to add `ExecStartPre=/usr/bin/podman rm -i -f bitwarden` if the process isn't cleaned up correctly. +If you want the container to have a specific name, you might need to add `ExecStartPre=/usr/bin/podman rm -i -f bitwarden` if the process isn't cleaned up correctly. Note that this method currently doesn't work with the `User=` options users (see https://github.com/containers/podman/issues/5572). # Troubleshooting ## Debugging systemd service file