podman.service: KillMode=process leaks pause process, breaks subsequent API invocations #7021
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.
/kind bug
Description
podman.service, in particular the user one, uses
KillMode=process
. When the unit stops, this leaves behind a processNot only is this a resource leak, it actively breaks the next time the API gets invoked.
Steps to reproduce the issue:
Make sure user's podman service is enabled:
Make an API request to start podman.service:
Log out the user
Ensure in
loginctl
(as root) that the user session is gone. Butpgrep -au
username still shows a leftover process:Log back in as the user
Do another API request, same curl command
Describe the results you received:
In (6), the API request hangs. In journalctl you see an repeated restart/failure:
Describe the results you expected:
podman.service stops cleanly, and restarts work.
Additional information you deem important (e.g. issue happens only occasionally):
I noticed this when enabling the user-container tests in cockpit-podman in Fedora dist-git gating.
pull request
As a workaround, I drop
KillMode
from the unit:Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):podman-2.1.0-0.77.dev.git60127cf.fc33.x86_64
Additional environment details (AWS, VirtualBox, physical, etc.):
Local Fedora Rawhide VM (from dist-git gating)
The text was updated successfully, but these errors were encountered: