You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In ops-devnet/docker-compose.yaml, set pid to host on kanvas-node.
kanvas-node:
pid: host
And then set ptrace_scope to 0
> sudo su -
>echo 0 > /proc/sys/kernel/yama/ptrace_scope
And then if I try to debug by attaching go process is rejected with this message.
Failed to attach: Could not attach to pid 39997: current user does not own the process.
Which feature do you want to expect?
I expect the process is launched with uid:gid so that we are able to debug. Currently, we should rely on the log message, which is very difficult when we consider that the logs are emitted so long.
The text was updated successfully, but these errors were encountered:
chokobole
changed the title
Support debugging by attaching go process which is ran by docker compose
Support debugging by attaching go process which is run by docker compose
Apr 11, 2023
This commit helps user to debug a process which is run by docker
compose. Currently, this only works on Linux. There should be another
way for macOS users.
Resolves: #11
Issue Type
Feature Request
Kroma Version
0.1.0
OS Platform and Distribution
Linux Ubuntu 22.04
Go version
go1.19.3 linux/amd64
Node version
No response
Current Behaviour?
In
ops-devnet/docker-compose.yaml
, setpid
tohost
onkanvas-node
.And then set
ptrace_scope
to0
And then if I try to debug by attaching go process is rejected with this message.
Which feature do you want to expect?
I expect the process is launched with
uid:gid
so that we are able to debug. Currently, we should rely on the log message, which is very difficult when we consider that the logs are emitted so long.The text was updated successfully, but these errors were encountered: