Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

isContainerCgroup() for linux doesn't work in certain scenarios #395

Closed
pemarko opened this issue Sep 20, 2023 · 2 comments
Closed

isContainerCgroup() for linux doesn't work in certain scenarios #395

pemarko opened this issue Sep 20, 2023 · 2 comments
Labels
question Further information is requested

Comments

@pemarko
Copy link

pemarko commented Sep 20, 2023

Describe the bug
Running local kind cluster, when ecapture is executed inside ubuntu:22.04 container, it fails to start as it cannot find /boot/config-*
Problem is detection in isContainerCgroup() which reads single 1024 chunk of /proc/1/cgroups and looks for "cpuset:/" substring. However in my case, substring is at byte1612.

To Reproduce
Run ecapture inside container on local kind cluster.

Expected behavior
ecapture should detect that's running inside container and thus won't require /boot/config* file to be present.

@cfc4n cfc4n added the question Further information is requested label Sep 21, 2023
@cfc4n
Copy link
Member

cfc4n commented Sep 21, 2023

Running ecapture in a container, file absence is not the main issue. There are also many problems related to the container's BPF execution permissions, library location, symbol table search, and so on. It is recommended that you use ecapture inside the host machine.

ref: #65

@cfc4n
Copy link
Member

cfc4n commented Oct 1, 2023

ping?

@cfc4n cfc4n closed this as completed Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants