gdb in docker

docker run -d –cap-add=SYS_PTRACE -p 8991:8999 …..

https://stackoverflow.com/questions/58590258/docker-run-cap-add-sys-ptrace-gets-invalid-reference-format-repository-name

docker exec –privileged -it mywebproxy_my-proxy_1 /bin/bash

https://stackoverflow.com/questions/42029834/gdb-in-docker-container-returns-ptrace-operation-not-permitted

https://stackoverflow.com/questions/58377469/difference-between-cap-add-net-admin-and-add-capabilities-in-yml

Difference between --privileged and --cap-add=all in docker

Setting privileged should modify:

capabilities: removing any capability restrictions
devices: the host devices will be visible
seccomp: removing restrictions on allowed syscalls
apparmor/selinux: policies aren’t applied
cgroups: I don’t believe the container is limited within a cgroup
That’s from memory, I might be able to find some more digging in the code if this doesn’t point you too your issue.

https://stackoverflow.com/questions/66635237/difference-between-privileged-and-cap-add-all-in-docker

https://stackoverflow.com/questions/30905674/newer-versions-of-docker-have-cap-add-what-caps-can-be-added

docker run –cap-add=SYS_PTRACE -it ubuntu:18.04 /bin/bash

https://jvns.ca/blog/2020/04/29/why-strace-doesnt-work-in-docker/

https://blog.csdn.net/liuqiuyuewo/article/details/80998850

https://github.com/tonyOreglia/argument-counter/wiki/How-to-use-GDB-within-Docker-Container

docker run –rm -it –cap-add=SYS_PTRACE –security-opt seccomp=unconfined -v “$(current_dir)”:/app -w /app