From 13259ceec68081d12f4c2faef5a72133c501ce39 Mon Sep 17 00:00:00 2001 From: Eugene Burkov Date: Tue, 18 Apr 2023 19:58:03 +0300 Subject: [PATCH] Pull request 167: 5713-healthcheck-warning Merge in GO/adguard-home-wiki from 5713-healthcheck-warning to master Squashed commit of the following: commit 214d775e6a4ca215565a5a3148df2c1b16255270 Author: Eugene Burkov Date: Tue Apr 18 19:24:48 2023 +0300 Docker: fix typos commit 9e449b4c721bc552206b919718316d071df02fd0 Author: Eugene Burkov Date: Tue Apr 18 19:13:06 2023 +0300 Docker: add known issues --- Docker.md | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/Docker.md b/Docker.md index e8ddc36..9f18cd2 100644 --- a/Docker.md +++ b/Docker.md @@ -224,3 +224,37 @@ your machine: ```sh systemctl reload-or-restart systemd-resolved ``` + + + +## Known issues + + ### Healthcheck + +Since **v0.107.28** the container uses Docker-provided healthcheck mechanism. +If the implementation of the healthcheck script causes any issues with custom +Docker images and orchestration tools (like [#5711], [#5713]), then we recommend +disabling it by adding `--no-healthcheck` to the `docker run` command or using +your tool's equivalent. + +(The actual change was made due to a necessity to handle zombie processes of +`wget` instances, see [PID 1 Docker problem][pid1]). + + + +[#5711]: https://github.com/AdguardTeam/AdGuardHome/issues/5711 +[#5713]: https://github.com/AdguardTeam/AdGuardHome/issues/5713 + +[pid1]: https://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zombie-reaping-problem