Bug: pod restarted after containerd restarted when container IO is huge

[Burning1020]

We have found a bug that pods restarted after containerd restarted, especially on the condition that the container IO is very frequent. The parent process of the container processm that is our async containerd
-shim process is not very careful to handle the pipe of container process IO. Thus when containerd restarts, some of containers, especially that has huge IO requests, would receive EPIPE and exited unexpectly.

[Burning1020]

We have to do some code optimization in handling container IO pipe in the async shim-runc crate, I can fix this lately.

[github-actions]

This issue is stale because it has been open 90 days with no activity. This issue will be closed in 7 days unless new comments are made or the stale label is removed.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.