Open jcvenegas opened 7 years ago
this is a regression from 2.x to 3.0
From @amshinde "I tried reproducing the issue and was able to do so. The command just hangs. But I do see that the file is successfully created inside the container with the right content, the container process does not seem to send the exit code to the shim process. I can verify this from the shim logs as well, the contents of the file are sent, but it never receives an exit code."
@jcvenegas good news, https://github.com/clearcontainers/proxy/pull/170 and https://github.com/clearcontainers/agent/pull/162 fix this issue. The root cause was both the proxy not redirecting empty messages, and the agent not handling the closure of stdin in such cases.
@jcvenegas I think this issue could be closed since clearcontainers/proxy#170 and clearcontainers/agent#162 have been merged. We might want to wait for the agent patch to reallly land into our clear-containers.img
though.
The following case is failing trying to send some date by through a pipe.
echo data | docker exec -i "${container}" bash -c "cat > /f"
Here a script to run and confirm. Note that it works for
runc
as runtime.