Failed to start in docker and binary mode.

[RedL1ghtning]

Since verision 1.19.0. I can`t start node-agent on nodes in docker and binary modes.

Jun 24 17:14:11 {NODE_NAME} systemd[1]: Starting Coroot node agent... Jun 24 17:14:11 {NODE_NAME} systemd[1]: Started Coroot node agent. Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.900580 27126 net.go:20] whitelisted public IPs: [0.0.0.0/0] Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.900925 27126 net.go:32] ephemeral-port-range: 32768-60999 Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.916259 27126 cilium.go:30] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_ct4_global: no such file or directory Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.916331 27126 cilium.go:36] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_ct6_global: no such file or directory Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.916355 27126 cilium.go:43] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_lb4_backends_v2: no such file or directory Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.916375 27126 cilium.go:43] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_lb4_backends_v3: no such file or directory Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.916396 27126 cilium.go:52] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_lb6_backends_v2: no such file or directory Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.916417 27126 cilium.go:52] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_lb6_backends_v3: no such file or directory Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.921120 27126 main.go:111] agent version: 1.20.2 Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.921349 27126 main.go:117] hostname: {NODE_NAME} Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.921369 27126 main.go:118] kernel version: 4.19.0-23-amd64 Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.921891 27126 main.go:75] machine-id: 7b5558e041cd47e098f6f36fb4221d91 Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.922073 27126 tracing.go:37] OpenTelemetry traces collector endpoint: {TRACES_ENDPOINT} Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.922247 27126 otel.go:29] OpenTelemetry logs collector endpoint: {LOGS_ENDPOINT} Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.922529 27126 metadata.go:67] cloud provider: Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.922569 27126 collector.go:157] instance metadata: <nil> Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: I0624 17:14:11.922787 27126 profiling.go:49] no profiles endpoint configured Jun 24 17:14:11 {NODE_NAME} coroot-node-agent[27126]: W0624 17:14:11.923370 27126 registry.go:79] Cannot connect to the Docker daemon at unix:///proc/1/root/run/docker.sock. Is the docker daemon running? Jun 24 17:14:15 {NODE_NAME} coroot-node-agent[27126]: W0624 17:14:15.926596 27126 registry.go:82] couldn't connect to containerd through the following UNIX sockets [/var/snap/microk8s/common/run/container Jun 24 17:14:15 {NODE_NAME} coroot-node-agent[27126]: W0624 17:14:15.926596 27126 registry.go:82] couldn't connect to containerd through the following UNIX sockets [/var/snap/microk8s/common/run/container Jun 24 17:14:15 {NODE_NAME} coroot-node-agent[27126]: W0624 17:14:15.927452 27126 registry.go:85] stat /proc/1/root/var/run/crio/crio.sock: no such file or directory Jun 24 17:14:16 {NODE_NAME} coroot-node-agent[27126]: E0624 17:14:16.206982 27126 tracer.go:191] load program: argument list too long: Jun 24 17:14:16 {NODE_NAME} coroot-node-agent[27126]: F0624 17:14:16.207094 27126 main.go:149] failed to load collection: program sys_enter_sendmmsg: load program: argument list too long Jun 24 17:14:16 {NODE_NAME} systemd[1]: coroot-node-agent.service: Main process exited, code=exited, status=1/FAILURE Jun 24 17:14:16 {NODE_NAME} systemd[1]: coroot-node-agent.service: Failed with result 'exit-code'.

My node name length is 48 symbols. I try to run node-agent on node with 36 symbols and it`s work. Can you increase limit for arguments?