gVisor stderr "broken pipe" EPIPE upon container closure

hello, there's this issue: https://github.com/google/gvisor/issues/2233

The issue is around cri-o and gVisor(runsc) containers using conmon, in the loggs attached to the mentioned issue there seems to be some process closing the stderr pipe before the container kernel receives the SIGKILL which results in a unclean exit of the container. cri-o has other runtimes (runc and kata-containers) registered which work fine for this case.

I opened this issue here for conmon devs to consider if this could be overcome from within conmon using some existing command-line arguments or maybe consider making one.

greetings.

Read the linked gVisor issue 2233 and its attached logs first, then inspect conmon’s stderr handling during container closure and compare it with cri-o’s runc and kata-containers behavior. Done means determining whether existing conmon command-line arguments can address the EPIPE or whether a conmon change is required.

Written by the indexing model from the issue text.