Hi Pany!
The podman run was an oversight on my part. Changing it to podman start is
something we definitely should change.
I'm not sure about the Type forking. When I looked around people either
used nothing - which defaults to simple - or used exec.
Though it seems to work just fine when I'm testing. If you know more than
me we can change that too, I see no harm in it
Thanks,
Eric Gustavsson
He / Him
Associate Software Engineer
Red Hat <
https://www.redhat.com>
IM: Telegram: @SpyTec
<
https://www.redhat.com>
On Tue, 6 Aug 2019 at 04:14, Pany <pany(a)fedoraproject.org> wrote:
Hi Eric,
I read your article on Fedora Magazine – "Manage your passwords with
Bitwarden and Podman"[1], which is really helpful! Thank you very
much!
Following your approach, I tried on my Fedora 30, step by step, which
led to a failure, unfortunately. At last, it turned out that maybe I
should do a little modification to your `bitwarden.service` file:
```
[Unit]
Description=Bitwarden Podman container
Wants=syslog.service
[Service]
Type=forking
User=my name
Group=my group
TimeoutStartSec=0
ExecStart=/usr/bin/podman start 'bitwarden'
ExecStop=-/usr/bin/podman stop -t 10 'bitwarden'
Restart=always
RestartSec=30s
KillMode=none
[Install]
WantedBy=multi-user.target
```
- I added `Type=forking` below the `[Service]` line or the process
would exited unexpectedly
- I changed `ExecStart` from `podman run` to `podman start` which
would make sure podman start the `bitwarden` container created
previously
I ain't a pro, and I'm not sure whether the modification is necessary
for others. If needed, I think this article could be updated.
[1]
https://fedoramagazine.org/manage-your-passwords-with-bitwarden-and-podman/