'Running Vaultwarden in a Container as a systemd Service Using Podman' linux linode
option tells that syslog should be started when our service is being started. However, it’s a weak requirement and the service will still start if syslog fails to start. In other words, we would like to have logs but it’s not mandatory for our service.sudo systemctl status vaultwarden.pod ● vaultwarden.pod.service - Vaultwarden/Bitwarden Server Loaded: loaded Active: active since Thu 2022-05-26 15:25:08 UTC; 1 day 20h ago Docs: https://github.
com/dani-garcia/vaultwarden Main PID: 19461 Tasks: 11 Memory: 26.9M CGroup: /system.slice/vaultwarden.pod.service ├─19461 /usr/bin/podman start -a vaultwarden.pod └─19574 /usr/libexec/podman/conmon --api-version 1 -c e2a6a794ddf8bb74308a9f64b98871913f6a46a8370c921dcb353f5db721cea0 -u e2a6a794ddf8bb74308a9f64b98871913f6a46a8370c921dcb353f5db721cea0 -r /usr/bin/crun -b /var/lib/containers/storage/overlay-containers/e2a6a7>sudo systemctl stop vaultwarden.pod sudo systemctl start vaultwarden.