From 7e4fd0f39497617465d86ce931aece94668e13ff Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Mon, 16 Dec 2024 17:31:59 +0100
Subject: [PATCH] engine: call out 0.0.0.0 as an option for metrics-addr

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
---
 content/manuals/engine/daemon/prometheus.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/content/manuals/engine/daemon/prometheus.md b/content/manuals/engine/daemon/prometheus.md
index a4dbdeb62108..5e194d627da4 100644
--- a/content/manuals/engine/daemon/prometheus.md
+++ b/content/manuals/engine/daemon/prometheus.md
@@ -48,8 +48,10 @@ Add the following configuration:
 Save the file, or in the case of Docker Desktop for Mac or Docker Desktop for
 Windows, save the configuration. Restart Docker.
 
-Docker now exposes Prometheus-compatible metrics on port 9323 on the loopback
-interface.
+Docker now exposes Prometheus-compatible metrics on port 9323 via the loopback
+interface. You can configure it to use the wildcard address `0.0.0.0` instead,
+but this will expose the Prometheus port to the wider network. Consider your
+threat model carefully when deciding which option best suits your environment.
 
 ### Create a Prometheus configuration