Failure to delete a VM #42
Comments
c3d
added a commit
to c3d/krunvm
that referenced
this issue
Jul 6, 2023
There are cases where krunvm fails to delete a VM, e.g. because the corresponding container no longer exists. Add a `--force` (or `-f`) option to the `delete` subcommand that forces deletion of the VM configuration in that case. Fixes: containers#42 Signed-off-by: Christophe de Dinechin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On
macOS, some of the VMs that are recorded in my configuration won't delete:Notice the empty
buildahoutput.buildahonly shows a restricted list of containers:The container for
debian-microVMis not there:% krunvm list [...] debian-microVM CPUs: 2 RAM (MiB): 1024 DNS server: 1.1.1.1 Buildah container: debian-working-container Workdir: /root Mapped volumes: {} Mapped ports: {} [...]In my VM list, many of my VMs have non-existent containers and fail the same way, e.g.:
fedora-rawhide CPUs: 4 RAM (MiB): 4096 DNS server: 1.1.1.1 Buildah container: fedora-working-container Workdir: /root Mapped volumes: {"/Users/ddd": "/root"} Mapped ports: {}What I find more concerning is that several VMs apparently share the same container. Is that normal?
bd-ubuntu CPUs: 8 RAM (MiB): 8192 DNS server: 1.1.1.1 Buildah container: ubuntu-working-container-1 Workdir: /ddd Mapped volumes: {"/Users/ddd/": "/ddd"} Mapped ports: {} ubuntu-test CPUs: 2 RAM (MiB): 1024 DNS server: 1.1.1.1 Buildah container: ubuntu-working-container-1 Workdir: Mapped volumes: {} Mapped ports: {}None of these VMs can be deleted using
krunvmtoday, because the error causes the configuration to not be updated. It might be useful to add a-foption to ignorebuildaherrors and delete entries in thekrunvmconfig anyway.The text was updated successfully, but these errors were encountered: