If you open a capture that contains the container event exec_die, the Sysdig Inspect UI remains blocked on the loading screen:
What happens under the hood is that the sysdig chisel used to define data for the Overview page fails:
davide sysdig: ./sysdig -r '/Users/davide/capture.scap' -c wsysdig_summary 400
{"slices": [
{"progress": 1.4986186694193 },
{"progress": 3.787689228383 },
wsysdig_summary chisel error: [string "--[[..."]:431: attempt to index a nil value
{"progress": 100, "data": {
"info":{
...
and the chisel error causes the UI to hang forever.
The failure in the chisel happens in the following line: https://github.com/draios/sysdig/blob/94ca2866ded8443b66fe912324fcef70f72c9337/userspace/sysdig/chisels/wsysdig_summary.lua#L431
The problem is that the Docker event exec_die is not listed as valid event and the analysis fails when the Docker event is read from the capture file. See moby/moby#35702 for more information about the event.
If you open a capture that contains the container event
exec_die, the Sysdig Inspect UI remains blocked on the loading screen:What happens under the hood is that the sysdig chisel used to define data for the Overview page fails:
and the chisel error causes the UI to hang forever.
The failure in the chisel happens in the following line: https://github.com/draios/sysdig/blob/94ca2866ded8443b66fe912324fcef70f72c9337/userspace/sysdig/chisels/wsysdig_summary.lua#L431
The problem is that the Docker event
exec_dieis not listed as valid event and the analysis fails when the Docker event is read from the capture file. See moby/moby#35702 for more information about the event.