Closed fuweid closed 2 years ago
critest will call CreateContainer and delete it. And then the fifo will be leaky.
The case name is runtime should support removing created container [Conformance].
runtime should support removing created container [Conformance]
reproduce:
critest -runtime-endpoint /run/containerd/containerd.sock -ginkgo.focus 'runtime should support removing created container'
The result is from v1.5.11 containerd (using runc-v2 shim). It is upstream issue. But block v0.1.0 release.
➜ testing sudo lsof -p $(pidof containerd) lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse file system /run/user/1000/doc Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME container 155110 root cwd DIR 259,2 4096 2 / container 155110 root rtd DIR 259,2 4096 2 / container 155110 root txt REG 259,2 47675128 8398013 /usr/bin/containerd container 155110 root mem-W REG 259,2 524288 17566340 /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/metadata.db container 155110 root mem-W REG 259,2 8388608 17575408 /var/lib/containerd/io.containerd.metadata.v1.bolt/meta.db container 155110 root mem REG 259,2 1983576 8391102 /usr/lib/x86_64-linux-gnu/libc-2.33.so container 155110 root mem REG 259,2 150720 8391620 /usr/lib/x86_64-linux-gnu/libpthread-2.33.so container 155110 root mem REG 259,2 22912 8391104 /usr/lib/x86_64-linux-gnu/libdl-2.33.so container 155110 root mem REG 259,2 216192 8391094 /usr/lib/x86_64-linux-gnu/ld-2.33.so container 155110 root 0r CHR 1,3 0t0 5 /dev/null container 155110 root 1u unix 0xffff9202e6745940 0t0 1957280 type=STREAM container 155110 root 2u unix 0xffff9202e6745940 0t0 1957280 type=STREAM container 155110 root 3u a_inode 0,14 0 12472 [eventpoll] container 155110 root 4r FIFO 0,13 0t0 1955442 pipe container 155110 root 5w FIFO 0,13 0t0 1955442 pipe container 155110 root 6uW REG 259,2 8388608 17575408 /var/lib/containerd/io.containerd.metadata.v1.bolt/meta.db container 155110 root 7u a_inode 0,14 0 12472 [eventpoll] container 155110 root 8r a_inode 0,14 0 12472 inotify container 155110 root 9u a_inode 0,14 0 12472 [eventpoll] container 155110 root 10r FIFO 0,13 0t0 1949683 pipe container 155110 root 11w FIFO 0,13 0t0 1949683 pipe container 155110 root 12u unix 0xffff920220e92a80 0t0 1949684 /run/containerd/debug.sock type=STREAM container 155110 root 13u unix 0xffff920220e96a40 0t0 1949685 /run/containerd/containerd.sock.ttrpc type=STREAM container 155110 root 14u unix 0xffff920220e91980 0t0 1949686 /run/containerd/containerd.sock type=STREAM container 155110 root 15uW REG 259,2 524288 17566340 /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/metadata.db container 155110 root 16u IPv4 1952557 0t0 TCP localhost:41601 (LISTEN) container 155110 root 23u FIFO 0,25 0t0 10010 /run/containerd/io.containerd.grpc.v1.cri/containers/36fc8dc0b6e479999877bf7fdafc83b26766c667df0bfe17f292ffe7ee04a885/io/2766993513/36fc8dc0b6e479999877bf7fdafc83b26766c667df0bfe17f292ffe7ee04a885-stdout (deleted) container 155110 root 24u FIFO 0,25 0t0 10011 /run/containerd/io.containerd.grpc.v1.cri/containers/36fc8dc0b6e479999877bf7fdafc83b26766c667df0bfe17f292ffe7ee04a885/io/2766993513/36fc8dc0b6e479999877bf7fdafc83b26766c667df0bfe17f292ffe7ee04a885-stderr (deleted)
critest will call CreateContainer and delete it. And then the fifo will be leaky.
The case name is
runtime should support removing created container [Conformance]
.reproduce:
The result is from v1.5.11 containerd (using runc-v2 shim). It is upstream issue. But block v0.1.0 release.