-
Notifications
You must be signed in to change notification settings - Fork 236
Closed
Labels
area/runtimebase functionalityBasic container functionality issueBasic container functionality issuekind/bugSomething isn't workingSomething isn't working
Description
[ec2-user@ip-172-31-30-18 ~]$ sudo /usr/local/bin/ctr run --snapshotter firecracker-naive --runtime aws.firecracker --tty docker.io/library/busybox:latest test
/ # echo hello
hello
/ # exit
[ec2-user@ip-172-31-30-18 ~]$ sudo /usr/local/bin/ctr c rm test
[ec2-user@ip-172-31-30-18 ~]$ sudo /usr/local/bin/ctr run --snapshotter firecracker-naive --runtime aws.firecracker --tty docker.io/library/busybox:latest test
ctr: mkdir /run/containerd/io.containerd.runtime.v2.task/default/test: file exists: unknown
Even though I've deleted the container (and its snapshot) on the host, the microVM rootfs the host retains the bundle directory that was created for the container. We should either clean up the bundle directory when the container is removed (or stopped?), or we should ensure that the microVM rootfs is read-only (or separate per microVM).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/runtimebase functionalityBasic container functionality issueBasic container functionality issuekind/bugSomething isn't workingSomething isn't working