diff --git a/develop-docs/self-hosted/troubleshooting/docker.mdx b/develop-docs/self-hosted/troubleshooting/docker.mdx
index 43ddedafe030aa..89cf04e70a6719 100644
--- a/develop-docs/self-hosted/troubleshooting/docker.mdx
+++ b/develop-docs/self-hosted/troubleshooting/docker.mdx
@@ -10,7 +10,7 @@ Around version 25.1.0 to 25.4.0, users which did not have `docker compose` plugi
 
 ## Container Healthcheck
 
-There may be some circumstances which you may want to increase or decrease healthcheck interval, timeout or retries for your custom needs. This can be achieved by editing `HEALTHCHECK_INTERVAL`, `HEALTHCHECK_TIMEOUT`, `HEALTHCHECK_RETRIES` variables' values in `.env`.
+There may be some circumstances where you want to increase or decrease the healthcheck interval, timeout, or retries for your custom needs. You can do this by overriding the `HEALTHCHECK_INTERVAL`, `HEALTHCHECK_TIMEOUT`, and `HEALTHCHECK_RETRIES` values from `.env` in a separate `.env.custom` file and running Docker Compose with both files (for example, `docker compose --env-file .env --env-file .env.custom up`).
 
 Occasionally, you might see an error like this
 ```
@@ -19,6 +19,23 @@ container for service "${servicename}" is unhealthy
 
 This can usually be resolved by running `docker compose down` and `docker compose up --wait` or rerunning the install script.
 
+<Alert title="Note"> 
+  On slower systems, including systems that only meet the minimum resource requirements for self-hosted Sentry, this issue may still persist even after rerunning `docker compose down` and `docker compose up --wait`.
+
+  In this case, you can override the healthcheck parameters defined in `.env` by setting custom values in `.env.custom`.
+
+  For example, increasing `HEALTHCHECK_RETRIES` may resolve the issue:
+
+```shell
+# .env.custom
+HEALTHCHECK_RETRIES=20
+```
+
+  Then start Docker Compose.
+
+  Depending on your system, you may also need to adjust other `HEALTHCHECK_*` values.
+</Alert>
+
 ## Docker Network Conflicting IP Address
 
 Self-hosted Sentry is using Docker's bridge networking, in which use a specific private IP range. By default, Docker uses `172.17.0.0/16` range (`172.17.0.0`-`172.17.255.255`). This may cause conflict with your private network. You can change Docker's default IP range by configuring the `/etc/docker/daemon.json` file. If the file does not exists, you can create it yourself.