Sysdig doesn't seem to capture read operations over container process #1 binary file

Open
#1,136 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, docker, linux
Domain
devtools, operating-systems

Research direction

Reproduce the issue with sysdig -pc container.name != host -w nginxdump and docker run -d -P nginx, then compare the capture with lsof inside the container for /usr/sbin/nginx. Trace the container process #1 file-read capture path and verify that the resulting capture reports the binary read operation.

Written by the indexing model from the issue text.

Description

feature-request pinned

Foe example, booting a new nginx container I don't get any file read operation over '/usr/sbin/nginx'

How to reproduce:

Start the capture using:

# sysdig -pc container.name != host -w nginxdump

A couple of seconds later I launch a new nginx cotainer:

# docker run -d -P nginx

The resulting capture doesn't contain any file read for '/usr/sbin/nginx', even though 'lsof' inside the container shows it.

Dominant language
C++
Stars
8.3k
Forks
753
No merged PRs in 30d

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.

More from draios/sysdig

All issues in draios/sysdig

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.