From 59ff44909f13897f5f4f02b431d96c829adb4ccd Mon Sep 17 00:00:00 2001
From: Dean Chen <862469039@qq.com>
Date: Mon, 17 Aug 2026 09:39:04 +0500
Subject: [PATCH] docs: show network=host for the docker-container builder

The custom-network section only had a user-defined overlay. Reaching
a host service needs network=host, which the default docker driver
cannot do.

Signed-off-by: Dean Chen <862469039@qq.com>
---
 .../build/builders/drivers/docker-container.md     | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/content/manuals/build/builders/drivers/docker-container.md b/content/manuals/build/builders/drivers/docker-container.md
index 28ceb4508ec4..02c04832f17f 100644
--- a/content/manuals/build/builders/drivers/docker-container.md
+++ b/content/manuals/build/builders/drivers/docker-container.md
@@ -165,6 +165,20 @@ $ docker inspect buildx_buildkit_mybuilder0 --format={{.NetworkSettings.Networks
 map[foonet:0xc00018c0c0]
 ```
 
+To reach a service on the host (for example a local registry or a
+development database), put the builder on the host network instead:
+
+```console
+$ docker buildx create --use --bootstrap \
+  --driver docker-container \
+  --name mybuilder \
+  --driver-opt network=host
+```
+
+The default `docker` driver cannot see Docker overlay networks. Use a
+`docker-container` builder with `network=host` (or a user-defined
+network, as above) when the build needs that connectivity.
+
 ## Further reading
 
 For more information on the Docker container driver, see the