Sebastien Boeuf
Sebastien Boeuf
I have tried to reproduce (many attempts) but both with image 19790 and 20120, I don't have any CRI-O issue. Maybe because I am trying inside a VM running on...
@jcvenegas could you investigate by enabling devicemapper. It might be a way to reproduce more easily.
kata-containers/runtime#200 has been merged !
@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...
@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`...
This works for me... ``` Server Version: 17.09.0-ce Storage Driver: overlay cc-runtime 3.0.8 ```
@miaoyq we actually don't want to provide the pid of the qemu process since this is related to the pod and not to the container itself. What we could do...
@grahamwhaley no idea on the top of my head, this needs further investigations.
@grahamwhaley oh nice and quick debug ! What's the next step ? Because it's 9p issue, does that mean we cannot expect this to work ?
@grahamwhaley using devmapper might solve this issue then (unless the file that needs to be accessed is passed through 9p as an extra mount on top of the rootfs).