Open jcvenegas opened 7 years ago
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" line=495 source="shim" name="cc-shim" msg="Frame read - HeaderLength: 3, Version: 2, Payloadlen: 62, Type:1, Opcode: 6, Err:16"
time="2017-10-26T14:55:07.393418323-0500" level="debug" pid=25034 function="handle_proxy_message" line=737 source="shim" name="cc-shim" msg="Received frame with type: 1, opcode: 6"
time="2017-10-26T14:55:07.393442110-0500" level="error" pid=25034 function="handle_proxy_response" line=616 source="shim" name="cc-shim" msg="Error response received from proxy at /var/run/clear-containers/proxy.sock: {\"msg\":\"received SIGWINCH but terminal size is invalid (0,0)\"}"
cc-proxy is not allowing to send that signal because of its values:
https://github.com/clearcontainers/proxy/blob/master/proxy.go#L451
Description of problem
https://github.com/clearcontainers/proxy/blob/master/proxy.go#L451
Expected result
Workload will get the signal if
docker kill 28
is used. Example:The contianer should exit after do
kill
, but looking at docker ps is still up.$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES fed26d7492f6 busybox "sh -c 'trap \"exit..." 8 minutes ago Up 8 minutes P1GjgyJuoQSVthDf1APV4lnjTauxd9
Actual result
The workload get the signal and in the example exits. (this works with
runc
)cc-data.txt
Meta details
Running
cc-collect-data.sh
version3.0.5 (commit 40047b5)
at2017-10-26.15:04:14.562059613
.Runtime is
/bin/cc-runtime
.cc-env
Output of "
/bin/cc-runtime cc-env
":Runtime config files
Runtime default config files
Runtime config file contents
Config file
/etc/clear-containers/configuration.toml
not found Output of "cat "/usr/share/defaults/clear-containers/configuration.toml"
":Logfiles
Runtime logs
Recent runtime problems found in global log
/var/lib/clear-containers/runtime/runtime.log
:Proxy logs
Recent proxy problems found in system journal: