podman generate systemd
service file fails to start container
#11264
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Note that this problem is only happening on my workstation, it does not reproduce in my test VMs.
My containers start fine using podman directly but when I attempt to start them via a
podman generate systemd
generated systemd user service file, they will not start. Using the default service file initially results in a pidfile error (see below) and after commenting out the pidfile= check, the service dies without successfully launching the container.Steps to reproduce the issue:
podman generate systemd --name sabnzbd --restart-policy no --container-prefix "" --separator "" > ~/.config/systemd/user/sabnzbd.service
to create the service file:systemctl --user daemon-reload && systemctl --user start sabnzbd
Describe the results you received:
Problem 1:
Problem 2:
If I comment out the PIDFile= line, attempting to start the container via the systemd service results in an inactive (dead) unit:
Describe the results you expected:
The service file works fine in my test VMs, giving the folliowing output:
Additional information you deem important (e.g. issue happens only occasionally):
Only happening on my workstation.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
I have tried using podman-3.2.x and podman podman-3.3.0-0.13.rc2
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: