From f01d6aefa999be2301eab25f83feff4408b255ce Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Mon, 19 Aug 2024 14:47:43 +0200
Subject: [PATCH] compose: use real network driver_opts examples

The examples provided for network driver opts with compose only
demonstrated placeholder, fictitious options. This changes the examples
to show a realistic example for the bridge driver.

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
---
 content/compose/networking.md              | 13 ++++++------
 content/reference/compose-file/networks.md | 23 +++++++++++-----------
 content/reference/compose-file/services.md |  7 ++++---
 3 files changed, 22 insertions(+), 21 deletions(-)

diff --git a/content/compose/networking.md b/content/compose/networking.md
index ff84474d43..86e83b9116 100644
--- a/content/compose/networking.md
+++ b/content/compose/networking.md
@@ -119,14 +119,13 @@ services:
 
 networks:
   frontend:
-    # Use a custom driver
-    driver: custom-driver-1
-  backend:
-    # Use a custom driver which takes special options
-    driver: custom-driver-2
+    # Specify driver options
+    driver: bridge
     driver_opts:
-      foo: "1"
-      bar: "2"
+      com.docker.network.bridge.host_binding_ipv4: "127.0.0.1"
+  backend:
+    # Use a custom driver
+    driver: custom-driver
 ```
 
 Networks can be configured with static IP addresses by setting the [ipv4_address and/or ipv6_address](/reference/compose-file/services.md#ipv4_address-ipv6_address) for each attached network.
diff --git a/content/reference/compose-file/networks.md b/content/reference/compose-file/networks.md
index b53edd783c..0fce1bd5f9 100644
--- a/content/reference/compose-file/networks.md
+++ b/content/reference/compose-file/networks.md
@@ -50,14 +50,13 @@ services:
 
 networks:
   frontend:
-    # Use a custom driver
-    driver: custom-driver-1
-  backend:
-    # Use a custom driver which takes special options
-    driver: custom-driver-2
+    # Specify driver options
+    driver: bridge
     driver_opts:
-      foo: "1"
-      bar: "2"
+      com.docker.network.bridge.host_binding_ipv4: "127.0.0.1"
+  backend:
+    # Use a custom driver
+    driver: custom-driver
 ```
 
 The advanced example shows a Compose file which defines two custom networks. The `proxy` service is isolated from the `db` service, because they do not share a network in common. Only `app` can talk to both.
@@ -80,16 +79,18 @@ For more information on drivers and available options, see [Network drivers](/en
 ### driver_opts
 
 `driver_opts` specifies a list of options as key-value pairs to pass to the driver. These options are
-driver-dependent. Consult the driver's documentation for more information. 
+driver-dependent.
 
 ```yml
 networks:
-  db-data:
+  frontend:
+    driver: bridge
     driver_opts:
-      foo: "bar"
-      baz: 1
+      com.docker.network.bridge.host_binding_ipv4: "127.0.0.1"
 ```
 
+Consult the [network drivers documentation](/engine/network/_index.md) for more information.
+
 ### attachable
 
 If `attachable` is set to `true`, then standalone containers should be able to attach to this network, in addition to services.
diff --git a/content/reference/compose-file/services.md b/content/reference/compose-file/services.md
index 2851f26339..388682df6c 100644
--- a/content/reference/compose-file/services.md
+++ b/content/reference/compose-file/services.md
@@ -563,7 +563,7 @@ dns_search:
 {{< introduced compose 2.27.1 "/compose/release-notes.md#2271" >}}
 
 `driver_opts` specifies a list of options as key-value pairs to pass to the driver. These options are
-driver-dependent. Consult the driver's documentation for more information.
+driver-dependent.
 
 ```yml
 services:
@@ -571,10 +571,11 @@ services:
     networks:
       app_net:
         driver_opts:
-          foo: "bar"
-          baz: 1
+          com.docker.network.bridge.host_binding_ipv4: "127.0.0.1"
 ```
 
+Consult the [network drivers documentation](/engine/network/_index.md) for more information.
+
 ### entrypoint
 
 `entrypoint` declares the default entrypoint for the service container.