ecapture: Kernel config read failed, error:Config not found
Describe the bug
the most recent ecapture build from master branch breaks with error
# ./bin/ecapture
2022/07/02 12:37:53 Kernel config read failed, error:Config not found, item:CONFIG_BPF.
To Reproduce Steps to reproduce the behavior:
- git clone the ecapture master branch
- make
- ./bin/ecapture
Expected behavior
should work
Screenshots
Linux Server/Android (please complete the following information):
- OS: centos 8 with custom kernel build
- Arch: x86
- Kernel Version: 5.18.0-rc3+
Additional context ecapture works before on this same machine with same kernel build
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16 (16 by maintainers)
Commits related to this issue
- pkg : fix Kernel config read failed, error:Config not found #117 Signed-off-by: CFC4N <cfc4n.cs@gmail.com> — committed to gojue/ecapture by cfc4n 2 years ago
- Merge pull request #123 from ehids/config-read-failed pkg : fix Kernel config read failed, error:Config not found #117 — committed to gojue/ecapture by cfc4n 2 years ago
- ebpf: remove detection of BPF config when running at container #127 remove detection of BPF config when running at container. In Github Action release.yml , qemu in docker ,do not have BPF config , ... — committed to gojue/ecapture by cfc4n 2 years ago
I don’t think so. New detection methods are necessary for container.
yes ,the code here is flawed. I’ll send a PR later. That is my fault, thannnnkkkksssss.