-
Notifications
You must be signed in to change notification settings - Fork 622
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
golang_pull :The agent cannot be started #2847
Comments
can you provide more info? docker version, os version & architecture, more agent logs, git revision where you try to run examples |
docker version:18.06.3-ce |
I dont understand. Do you run example from pyroscope github repo or something from your repo? Share full agent logs please |
My steps are as follows: |
ok, my bet is that you have toooooo old docker version which has seccomp policy blocking some syscalls unknown to it and new golang version is using these syscalls. you can verify this by running agent container with If it does help, I suggest you to update docker and libseccomp. |
ok, I got it |
Describe the bug
The agent cannot be started. An error occurs
I used the examples/golang-pull/static/docker-compose.yml file and started with docker-compose up -d, but the agent container failed to start and exited
To Reproduce
Steps to reproduce the behavior:
In examples/golang-pull/static/, run docker-compose up -d
Expected behavior
Application performance data can be successfully captured on pyroscope server, resulting in only pyroscope's own
Additional Context
The log information about the agent startup failure is as follows:
The text was updated successfully, but these errors were encountered: