From 1f77aba6f2d6fde31a25e1dc7a046e29969dad33 Mon Sep 17 00:00:00 2001 From: yubiuser Date: Sat, 9 Nov 2024 17:27:40 +0100 Subject: [PATCH] Add missing word Co-authored-by: RD WebDesign Signed-off-by: yubiuser --- docs/ftldns/debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ftldns/debugging.md b/docs/ftldns/debugging.md index 756cbfd8..4ffb9cf2 100644 --- a/docs/ftldns/debugging.md +++ b/docs/ftldns/debugging.md @@ -7,7 +7,7 @@ Once you are used to it, you can skip most of the steps. Debugging *FTL*DNS is q !!! info "When running Pi-hole in a Docker container" - If you are running Pi-hole in a Docker container, you will to perform all the steps described here *inside* the Docker container. You can use, e.g., `docker exec -it /bin/bash` to get a shell inside the container. + If you are running Pi-hole in a Docker container, you will need to perform all the steps described here *inside* the Docker container. You can use, e.g., `docker exec -it /bin/bash` to get a shell inside the container. You will also need to (temporarily!) add the `SYS_PTRACE` capability. This is required to allow `gdb` to attach to the `pihole-FTL` process inside the container. You can do this by starting the container with the `--cap-add=SYS_PTRACE` option. Furthermore, you need to disable the Linux kernel's secure computing mode for the container. Add `--security-opt seccomp:unconfined` in order to allow `gdb` to disable address space randomization.