Carlos Venegas

@miaoyq what is network configuration you are using for k8s? @mcastelino @sameo @sboeuf to me looks like the host net interfaces are in the namespace where the container is running....

@chavafg can you confirm this happend with all distros or just in fedora. I tried to reproduce it in ubuntu 16.04 and cc-runtime list is still working and not qemu...

@chavafg , Great that narrows the search space. So by looking at ``` time="2018-01-08T15:49:53Z" level=error msg="Container not running, impossible to signal the container" source=runtime time="2018-01-08T15:49:53Z" level=error msg="Container 699f5cc51b188a422cb385d0264f736cc2c34d36572631f97a9ee0b744804fb8 not ready...

I tested the image locally using this tests and the tests is passing. Btw seems that the tests is wrong with the new agent changes and older we never pass...

``` ok 12 ctr execsync not ok 13 ctr device add # (in test file crio.bats, line 530) # `[[ "$output" =~ "/dev/mynull" ]]' failed # 0 # time="2018-01-04 21:24:12.206637296Z"...

A new PR was send to agent repository https://github.com/clearcontainers/agent/pull/188 But seems that the crio tests are failing randomly ``` not ok 11 ctr execsync conflicting with conmon flags parsing #...

@sboeuf thanks for clarify about clearcontainers/agent#188. I also tested with image 20110 but not issues. I am testing locally in a cclouvm instance running ubuntu 16.04 but I can not...

@sboeuf yes, I will try it

No, locally I can not reproduce it devicemapper

cc shim logs shows that proxy return an error. ``` time="2017-10-26T14:55:07.392943628-0500" level="debug" pid=25034 function="send_proxy_message" line=300 source="shim" name="cc-shim" msg="Sending frame of type:0, opcode:6, payload:{\"signalNumber\": 28, \"rows\":0, \"columns\":0}" time="2017-10-26T14:55:07.393403655-0500" level="debug" pid=25034 function="read_frame"...