draios / draios/sysdig-inspect

Unable to open capture containing the container event `exec_die`

Open
#60 0 comments 0 reactions 1 assignee View on GitHub

@davideschiera is already working on this.

Since Jul 29, 2019.

type: bug
Dominant language
JavaScript
Stars
1k
Forks
76
PR merge metrics
No merged PRs in 30d

Description

If you open a capture that contains the container event exec_die, the Sysdig Inspect UI remains blocked on the loading screen:

image

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 https://github.com/moby/moby/issues/35702 for more information about the event.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.