Skip to content

SIGTERM doesn't kill containerd-shims #386

Closed

Description

If you run containerd as a systemd service, and you try to restart the service while containers are running the systemctl restart containerd will block because while containerd (the daemon) exits when it gets a SIGTERM it doesn't attempt to kill any of the containerd-shims -- which then causes systemd to SIGKILL them after 10 seconds (or whatever the timeout is).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions