Stop Docker published ports from bypassing the UFW firewall
The security problem, the chain explanation (DOCKER/DOCKER-USER evaluated before UFW's INPUT rules), the loopback-binding containment, ufw-docker (present in the AUR, last updated 2026-02) and the warning against "iptables": false are all accurate and still current on Docker 28/29. The Omarchy-specific sentence in the cause is stale: Omarchy 4 ships ufw-docker in its base package list and runs ufw-docker install during installation (install/config/firewall.sh), so Quattro is NOT the false-sense-of-protection case the record claims. Pasting yay -S ufw-docker && sudo ufw-docker install there re-applies rules that already exist and tells the reader the wrong thing about their machine.
Do NOT "fix" this by setting "iptables": false in /etc/docker/daemon.json unless you know what you are doing. That disables all of Docker's rule management and container outbound networking/NAT will break.
Symptom
UFW says my firewall is active and only SSH is allowed, but a container started with -p 8080:80 is reachable from every machine on my LAN (and from the internet if the box is exposed). sudo ufw status looks correct and yet the port is wide open.
Cause
Docker in its default mode writes its own iptables/nftables rules into the DOCKER and DOCKER-USER chains, which are evaluated for forwarded traffic before UFW's INPUT rules ever apply, so a published port is reachable regardless of ufw status. This affects any Arch box running ufw + Docker. Note that Omarchy 4 (Quattro) already ships ufw-docker and runs ufw-docker install at install time, so the DOCKER-USER block is normally present there. Check before assuming you are exposed.
Fix
First check whether the protection is already installed (it is by default on Omarchy 4):
sudo ufw-docker check
sudo iptables -S DOCKER-USER
grep -n 'ufw-docker' /etc/ufw/after.rules
If the DOCKER-USER block is missing (plain Arch, EndeavourOS, CachyOS), install it:
yay -S ufw-docker
sudo ufw-docker install
sudo systemctl restart ufw # or: sudo ufw reload
Then allow individual containers explicitly (sudo ufw-docker allow <container-name> 80/tcp). The loopback-binding containment ("127.0.0.1:8080:80") and the "iptables": false warning stand as written.
Verify
From another machine on the LAN: nc -vz <host-ip> 8080 is refused/times out for ports you did not explicitly allow, and succeeds for the ones you did. sudo iptables -S DOCKER-USER shows the ufw-docker rules.