mirror of
https://github.com/dani-garcia/vaultwarden
synced 2024-09-27 12:58:58 +02:00
Fixed some problems with the "New container every restart" chapter
parent
b6a7ce1c2a
commit
a463ff657c
1 changed files with 3 additions and 3 deletions
|
@ -35,8 +35,8 @@ If we want to create a new container every time the service starts we can edit t
|
||||||
[Service]
|
[Service]
|
||||||
Restart=on-failure
|
Restart=on-failure
|
||||||
ExecStartPre=/usr/bin/rm -f /%t/%n-pid /%t/%n-cid
|
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
|
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 --cid-file /%t/%n-cid
|
ExecStop=/usr/bin/podman rm -f --cidfile /%t/%n-cid
|
||||||
KillMode=none
|
KillMode=none
|
||||||
Type=forking
|
Type=forking
|
||||||
PIDFile=/%t/%n-pid
|
PIDFile=/%t/%n-pid
|
||||||
|
@ -46,7 +46,7 @@ Where `bitwarden.conf` environment file can contain all the container environmen
|
||||||
ROCKET_PORT=8080
|
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
|
# Troubleshooting
|
||||||
## Debugging systemd service file
|
## Debugging systemd service file
|
||||||
|
|
Loading…
Reference in a new issue