8000 nerdctl rm -f does not work with containers in unknown state · Issue #11890 · containerd/containerd · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
nerdctl rm -f does not work with containers in unknown state #11890
Closed
@apostasie

Description

@apostasie

Description

-f states that Force the removal of a running|paused|unknown container (uses SIGKILL)"

However:

sudo nerdctl ps -a

CONTAINER ID    IMAGE                                                 COMMAND                  CREATED           STATUS     PORTS                     NAMES
7a78c9746422    docker.io/dubodubonduponey/dns:bookworm-2024-09-01    "/boot/entrypoint.sh"    14 minutes ago    Unknown    0.0.0.0:4242->4242/tcp    dns
sudo nerdctl rm -f 7a78c9746422
ERRO[0004] 1 errors:
unknown container status unknown

and the container is still there.

Steps to reproduce the issue

Manage to get a container into a broken / unknown state (typically by making sure it fails during onCreateRuntime <- pick your favorite network bug to trigger this).

Then try to rm -f.

Describe the results you received and expected

Work.

What version of nerdctl are you using?

main

Are you using a variant of nerdctl? (e.g., Rancher Desktop)

None

Host information

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0