From b215d8ee7b7eb23239f4bb1d5eaeebcca6fed742 Mon Sep 17 00:00:00 2001
From: Dean Chen <862469039@qq.com>
Date: Mon, 17 Aug 2026 20:50:50 +0500
Subject: [PATCH 1/2] docs: point user-defined bridges at the firewalld zone
 note

Signed-off-by: Dean Chen <862469039@qq.com>
---
 content/manuals/engine/network/drivers/bridge.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/content/manuals/engine/network/drivers/bridge.md b/content/manuals/engine/network/drivers/bridge.md
index 74c452defd22..cbc1f0cbd8e8 100644
--- a/content/manuals/engine/network/drivers/bridge.md
+++ b/content/manuals/engine/network/drivers/bridge.md
@@ -199,6 +199,11 @@ $ docker network rm my-net
 > details should be considered implementation details. Let Docker manage your
 > user-defined networks for you.
 
+On hosts running [firewalld](https://firewalld.org), Docker puts its bridge
+devices in a `docker` zone. If containers on a user-defined bridge cannot
+reach each other, see
+[Packet filtering and firewalls](../packet-filtering-firewalls.md#integration-with-firewalld).
+
 ## Connect a container to a user-defined bridge
 
 When you create a new container, you can specify one or more `--network` flags.

From 87766478c355932ed2c360452b9436344b9b0463 Mon Sep 17 00:00:00 2001
From: Dean Chen <862469039@qq.com>
Date: Tue, 18 Aug 2026 00:42:54 +0500
Subject: [PATCH 2/2] chore: retrigger CI after Vale action 429

Signed-off-by: Dean Chen <862469039@qq.com>