Skip to content

Agate container does not respond to SIGINT and SIGTERM #418

@LogExE

Description

@LogExE

When started as a container, the server can't be stopped using Ctrl-C combination. The workaround is to type podman stop <container_id> in separate shell session. Podman waits 10 seconds for SIGTERM and then resorts to SIGKILL, finally stopping the server.

$ podman run --rm -p 1965:1965 ghcr.io/mbrubeck/agate:latest --hostname example.com
[2025-12-13T10:42:51Z INFO  agate] No certificate or key found for "example.com", generating them.
[2025-12-13T10:42:51Z INFO  agate] Started listener on 0.0.0.0:1965
^C^C^C^C^C

Workaround:

$ podman stop suspicious_chatelet 
WARN[0010] StopSignal SIGTERM failed to stop container suspicious_chatelet in 10 seconds, resorting to SIGKILL 
suspicious_chatelet

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