Add missing word
editorconfig-checker / editorconfig-checker (push) Has been cancelled
Check for merge conflicts / main (push) Has been cancelled

Co-authored-by: RD WebDesign <github@rdwebdesign.com.br>
Signed-off-by: yubiuser <github@yubiuser.dev>
This commit is contained in:
yubiuser
2024-11-09 17:27:40 +01:00
committed by GitHub
parent 5a9b17e8ca
commit 1f77aba6f2
+1 -1
View File
@@ -7,7 +7,7 @@ Once you are used to it, you can skip most of the steps. Debugging *FTL*DNS is q
<!-- markdownlint-disable code-block-style -->
!!! 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 <container_name> /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 <container_name> /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.