Skip to content

Podman escalates to SIGKILL because containerized process does not exit on SIGTERM #33

Description

@x80486

When stopping a docker.io/datawookie/medusa-proxy:0.2.2 container, Podman logs that SIGTERM failed and resorts to SIGKILL.

$ podman compose down --volumes 
WARN[0015] StopSignal SIGTERM failed to stop container tor-proxy in 15 seconds, resorting to SIGKILL 
tor-proxy
tor-proxy
d9d7e172468d21c2279178694a9734d4d1912d3dea054922ac033931c6acfb67
tor-network

Increasing stop_grace_period (timeout) does not help.

I can only guess that somehow, the the process inside the container is not quite sending the correct signal back.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions