Why use FIFO IO directly #238
Replies: 3 comments
-
@abel-von @mxpv @Burning1020 |
Beta Was this translation helpful? Give feedback.
-
As mentioned here: #24 (comment) |
Beta Was this translation helpful? Give feedback.
-
but the exec process will occupy the fifo io , so the containerd in execsync function will loop forver ,in test "TestContainerDrainExecIOAfterExit " .how can we resolve this problem . that's why I pull this pr #235 . How to report errors at the underlying runtime , the runc can't trace the daemon like "sleep 365d &" , and |
Beta Was this translation helpful? Give feedback.
-
I find this issus from
https://github.com/containerd/containerd/issues/9568
The community shim links child procress through copyIO. The shim and containerd have separate pipe links, so the shim can close the pipe when the exec process exit. r-shim use the FIFO-IO directly.
Beta Was this translation helpful? Give feedback.
All reactions