Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

ignite rm -f fails on dead/crashed container #751

Closed
bboreham opened this issue Dec 17, 2020 · 2 comments · Fixed by #809
Closed

ignite rm -f fails on dead/crashed container #751

bboreham opened this issue Dec 17, 2020 · 2 comments · Fixed by #809
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@bboreham
Copy link
Contributor

I was having issues which meant things had crashed; however I expect that there is some way to remove all reference to a VM rather than just complaining it can't be done.

# ignite ps
VM ID                   IMAGE                           KERNEL                                  SIZE    CPUS    MEMORY          CREATED STATUS  IPS             PORTS   NAME
0fdf2b2651969a6b        weaveworks/ignite-ubuntu:20.04  weaveworks/ignite-kernel:4.19.125       4.0 GB  1       512.0 MB        19m ago Up 19m  10.1.2.23               silent-wildflower
33f2f348e0669522        weaveworks/ignite-ubuntu:20.04  weaveworks/ignite-kernel:4.19.125       4.0 GB  1       512.0 MB        15h ago Up 15h  10.1.2.20               billowing-night
8a4bfc4d66ecb348        weaveworks/ignite-ubuntu:20.04  weaveworks/ignite-kernel:4.19.125       4.0 GB  1       512.0 MB        40m ago Up 40m  10.1.2.21               aged-sun
d630446df4ba2d11        weaveworks/ignite-ubuntu:20.04  weaveworks/ignite-kernel:4.19.125       4.0 GB  1       512.0 MB        21m ago Up 21m  10.1.2.22               cold-water
# 
root@bm01-ig:/home/vagrant# ignite rm -f 8a4bfc4d66ecb348        
INFO[0000] Removing the container with ID "ignite-8a4bfc4d66ecb348" from the "cni" network 
INFO[0000] CNI failed to retrieve network namespace path: no running task found: task ignite-8a4bfc4d66ecb348 not found: not found 
FATA[0000] failed to kill container for VM "8a4bfc4d66ecb348": no running task found: task ignite-8a4bfc4d66ecb348 not found: not found 
# ignite ps
VM ID                   IMAGE                           KERNEL                                  SIZE    CPUS    MEMORY          CREATED STATUS  IPS             PORTS   NAME
0fdf2b2651969a6b        weaveworks/ignite-ubuntu:20.04  weaveworks/ignite-kernel:4.19.125       4.0 GB  1       512.0 MB        19m ago Up 19m  10.1.2.23               silent-wildflower
33f2f348e0669522        weaveworks/ignite-ubuntu:20.04  weaveworks/ignite-kernel:4.19.125       4.0 GB  1       512.0 MB        15h ago Up 15h  10.1.2.20               billowing-night
8a4bfc4d66ecb348        weaveworks/ignite-ubuntu:20.04  weaveworks/ignite-kernel:4.19.125       4.0 GB  1       512.0 MB        41m ago Up 41m  10.1.2.21               aged-sun
d630446df4ba2d11        weaveworks/ignite-ubuntu:20.04  weaveworks/ignite-kernel:4.19.125       4.0 GB  1       512.0 MB        22m ago Up 22m  10.1.2.22               cold-water
@darkowlzz darkowlzz added the kind/bug Categorizes issue or PR as related to a bug. label Jan 4, 2021
@casibbald
Copy link

casibbald commented Jan 22, 2021

additionally
Ignite still seems to keep an entry somewhere of a VM even after being killed by ctr.

vagrant@ignite-dt-poc:~$ sudo ignite ps
VM ID			IMAGE				KERNEL					SIZE	CPUS	MEMORY		CREATED	STATUS	IPS		PORTS	NAME

af99123d59c0fbec	weaveworks/ignite-ubuntu:latest	weaveworks/ignite-kernel:4.19.125	4.0 GB	1	512.0 MB	10m ago	Up 10m	172.16.128.5		test112
vagrant@ignite-dt-poc:~$ sudo ignite rm af99123d59c0fbec

FATA[0000] af99123d59c0fbec is running
vagrant@ignite-dt-poc:~$ sudo ignite stop af99123d59c0fbec

INFO[0000] Removing the container with ID "ignite-af99123d59c0fbec" from the "cni" network

INFO[0000] CNI failed to retrieve network namespace path: container "ignite-af99123d59c0fbec" in namespace "firecracker": not found

FATA[0000] failed to stop container for VM "af99123d59c0fbec": container "ignite-af99123d59c0fbec" in namespace "firecracker": not found
vagrant@ignite-dt-poc:~$ sudo ctr -n firecracker containers ls

CONTAINER                           IMAGE                                 RUNTIME

test111-24g5h68-af99123d59c0fbec    docker.io/weaveworks/ignite:v0.8.0    io.containerd.runc.v2
vagrant@ignite-dt-poc:~$ sudo ctr -n firecracker container rm test111-24g5h68-af99123d59c0fbec

vagrant@ignite-dt-poc:~$ sudo ctr -n firecracker containers ls

CONTAINER                           IMAGE                                 RUNTIME
vagrant@ignite-dt-poc:~$ sudo ignite ps
VM ID			IMAGE				KERNEL					SIZE	CPUS	MEMORY		CREATED	STATUS	IPS		PORTS	NAME

af99123d59c0fbec	weaveworks/ignite-ubuntu:latest	weaveworks/ignite-kernel:4.19.125	4.0 GB	1	512.0 MB	30m ago	Up 30m	172.16.128.5		test112

@stealthybox
Copy link
Contributor

:)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants