Binary IO process early termination behavior

[henry118]

I recently came across an issue related to binary IO. Basically my IO binary process could terminate unexpectedly before the container process exits. Hence the following questions:

1. When the shim spawns the binary IO process, it will block until the IO process notifies its readiness here. For notification, the logic is simply closing the wait pipe and the shim will get io.EOF which is expected and ignored. However if the IO process terminates early, shim will also get io.EOF and continue to create the task. I wonder if we can distinguish the two cases and fail the task creation if the binary IO process exits?
2. Assuming the binary IO process terminates in the middle of a running container, what should be the expected behavior in this case? Should the container be terminated or they are expected to handle such case on their own?

Thanks for the advice.