-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Got "couldn't init manager error" when launching ecapture in docker container. #403
Comments
what's your docker launched command? |
Have you granted SYS_ADMIN permissions to Docker? e.g. : If you encounter any other issues while using eCapture in a container, you can refer to #65. |
Thanks for the suggestion. I did not add the |
Sorry for the late reply. Then I ran the same x64-based image on my own Macbook Pro (M1) laptop with Rosetta2 for automatic instruction translation, with the
The output was as follows:
I can notice that the error message has changed, but it still failed to start, indicating "...function not implemented...". I suspect that the eBPF feature is not fully supported by the macOS kernel on my Macbook Pro. Since the serverless service I mainly use on the cloud does not allow me to add admin privileges to the Docker container instances, I may not use ecapture in this scenario for now. If I ever need to do something similar on a VPS machine that I can manage myself, I will follow the instructions in issue:#65 and try using ecapture, which should work I guess. Thanks anyway! |
The The host kernel in macOS differs from Linux and does not support eBPF features. For security issues arising from granting |
Trying to run ecapture from cmd line, in a Docker container, as root. It emits error:
It seems all of three possible tls hooking modules failed to run. And all of those point to a same error:
couldn't init manager error:operation not permitted , couldn't adjust RLIMIT_MEMLOCK
To Reproduce
Steps to reproduce the behavior:
Just download ecapture binary(amd64 version), then unzip it and run the command in a bash repl.
Expected behavior
Screenshots
Linux Server/Android (please complete the following information):
KUBERNETES_SERVICE_PORT=6443
HOSTNAME=test-xhunterbase-56b679589-w7nmz
LANGUAGE=en_US.UTF-8
TEST_XHUNTERBASE_SVC_PORT_22_TCP=tcp://172.21.10.6:22
JAVA_HOME=/opt/jdk
PWD=/tmp/ecapture-v0.6.3-linux-x86_64
LS_OPTIONS=--color=auto
TEST_XHUNTERBASE_SVC_PORT_22_TCP_PORT=22
HOME=/root
LANG=en_US.UTF-8
KUBERNETES_PORT_443_TCP=tcp://172.21.0.1:443
TEST_XHUNTERBASE_SVC_PORT_10000_TCP_PORT=10000
TEST_XHUNTERBASE_SVC_PORT_10000_TCP=tcp://172.21.10.6:10000
TEST_XHUNTERBASE_SVC_PORT_10000_TCP_ADDR=172.21.10.6
TEST_XHUNTERBASE_SVC_PORT_10000_TCP_PROTO=tcp
TERM=xterm-256color
TEST_XHUNTERBASE_SVC_PORT_22_TCP_ADDR=172.21.10.6
aliyun_log_crd_user_defined_id=k8s-group-c3e4daee1064f4158891f67a0e996ef7a
SHLVL=2
TEST_XHUNTERBASE_SVC_PORT=tcp://172.21.10.6:22
KUBERNETES_PORT_443_TCP_PROTO=tcp
KUBERNETES_PORT_443_TCP_ADDR=172.21.0.1
TEST_XHUNTERBASE_SVC_PORT_22_TCP_PROTO=tcp
TEST_XHUNTERBASE_SVC_SERVICE_PORT_TEST_XHUNTERBASE_SVC_22_22=22
TEST_XHUNTERBASE_SVC_SERVICE_PORT_TEST_XHUNTERBASE_SVC_10000_10000=10000
TEST_XHUNTERBASE_SVC_SERVICE_PORT=22
KUBERNETES_SERVICE_HOST=172.26.19.176
LC_ALL=en_US.UTF-8
KUBERNETES_PORT=tcp://172.21.0.1:443
KUBERNETES_PORT_443_TCP_PORT=443
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/jdk/bin
TEST_XHUNTERBASE_SVC_SERVICE_HOST=172.21.10.6
OLDPWD=/tmp
_=/usr/bin/env
Additional context
I'm running a debian 11 linux image in a docker container.
The text was updated successfully, but these errors were encountered: