From 9e8a12aebe53bc07803a3af7488728f7e640e746 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?St=C3=A9phane=20Graber?= Date: Mon, 12 Aug 2024 14:02:30 -0400 Subject: [PATCH] doc/firewalld: Update Docker link MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Stéphane Graber --- doc/howto/network_bridge_firewalld.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/howto/network_bridge_firewalld.md b/doc/howto/network_bridge_firewalld.md index f59c1fc3b73..9d8d084f530 100644 --- a/doc/howto/network_bridge_firewalld.md +++ b/doc/howto/network_bridge_firewalld.md @@ -111,7 +111,7 @@ sudo ufw route allow in on incusbr0 from "${CIDR6}" Running Incus and Docker on the same host can cause connectivity issues. A common reason for these issues is that Docker sets the global FORWARD policy to `drop`, which prevents Incus from forwarding traffic and thus causes the instances to lose network connectivity. -See [Docker on a router](https://docs.docker.com/network/iptables/#docker-on-a-router) for detailed information. +See [Docker on a router](https://docs.docker.com/engine/network/packet-filtering-firewalls/#docker-on-a-router) for detailed information. There are different ways of working around this problem: