grafana
golang_pull :The agent cannot be started
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:
can you provide more info? docker version, os version & architecture, more agent logs, git revision where you try to run examples
provide
docker version:18.06.3-ce docker-compose version: 1.29.2 os: linux git version :1.8.3.1 I am running on a linux operating system, directly clone our gitlab code, using the docker-compose.yml file on gitlab to boot The file path is：https://github.com/grafana/pyroscope/blob/main/examples/golang-pull/static/docker-compose.yml
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： On a linux server 1、git clone https://github.com/grafana/pyroscope.git 2、cd pyroscope/examples/golang-pull/static 3、run docker-compose up -d 4、run docker-compose ps Displays the startup status and finds that the agent container fails to be started The following log indicates that the agent container fails to start： agent_1 | runtime/cgo: pthread_create failed: Operation not permitted agent_1 | SIGABRT: abort agent_1 | PC=0x7fe44d7e552b m=0 sigcode=18446744073709551610 agent_1 | agent_1 | goroutine 0 [idle]: agent_1 | runtime: g 0: unknown pc 0x7fe44d7e552b agent_1 | stack: frame={sp:0x7fff5497de80, fp:0x0} stack=[0x7fff5417f300,0x7fff5497e310) agent_1 | 0x00007fff5497dd80: 0x0000000000000000 0x0000000000000000 agent_1 | 0x00007fff5497de70: 0x0000000000000000 0x00007fe44d7e551e agent_1 | 0x00007fff5497de80: <0x0000000000000000 0xbb817044c78c5700 agent_1 | 0x00007fff5497de90: 0x0000000000000006 0x00007fe44d751740 agent_1 | 0x00007fff5497dea0: 0x0000000000000001 0x00007fff5497e150 agent_1 | 0x00007fff5497deb0: 0x000000000cf3e0e0 0x00007fe44d7903b6 agent_1 | 0x00007fff5497dec0: 0x00007fe44d94be90 0x00007fe44d77687c agent_1 | 0x00007fff5497ded0: 0x0000000000000020 0x0000000000000000 agent_1 | runtime: g 0: unknown pc 0x7fe44d7e552b agent_1 | stack: frame={sp:0x7fff5497de80, fp:0x0} stack=[0x7fff5417f300,0x7fff5497e310) agent_1 | 0x00007fff5497dd80: 0x0000000000000000 0x0000000000000000 agent_1 | 0x00007fff5497dd90: 0x0000000000000000 0x0000000000000000 agent_1 | 0x00007fff5497de80: <0x0000000000000000 0xbb817044c78c5700 agent_1 | 0x00007fff5497de90: 0x0000000000000006 0x00007fe44d751740 agent_1 | 0x00007fff5497dea0: 0x0000000000000001 0x00007fff5497e150 agent_1 | 0x00007fff5497deb0: 0x000000000cf3e0e0 0x00007fe44d7903b6 agent_1 | 0x00007fff5497dec0: 0x00007fe44d94be90 0x00007fe44d77687c agent_1 | agent_1 | goroutine 1 [running]: agent_1 | runtime.systemstack_switch() agent_1 | /usr/local/go/src/runtime/asm_amd64.s:474 +0x8 fp=0xc0000bc740 sp=0xc0000bc730 pc=0x4729e8 agent_1 | runtime.main() agent_1 | /usr/local/go/src/runtime/proc.go:169 +0x6d fp=0xc0000bc7e0 sp=0xc0000bc740 pc=0x4409ad agent_1 | runtime.goexit() agent_1 | /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc0000bc7e8 sp=0xc0000bc7e0 pc=0x4749c1 agent_1 | agent_1 | rax 0x0 agent_1 | rbx 0x1 agent_1 | rcx 0xffffffffffffffff agent_1 | rdx 0x6 agent_1 | rdi 0x1 agent_1 | rsi 0x1 agent_1 | rbp 0x6 agent_1 | rsp 0x7fff5497de80 agent_1 | r8 0x0 agent_1 | r9 0x0 agent_1 | r10 0x8 agent_1 | r11 0x246 agent_1 | r12 0x1 agent_1 | r13 0x16 agent_1 | r14 0xcf3e0e0 agent_1 | r15 0x6 agent_1 | rip 0x7fe44d7e552b agent_1 | rflags 0x246 agent_1 | cs 0x33 agent_1 | fs 0x0 agent_1 | gs 0x0
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 --security-opt seccomp=unconfined
If it does help, I suggest you to update docker and libseccomp. If you have to run old docker, then try to run with seccomp policy from new docker.