Repository files navigation

• English
• 中文

Please take a look atSolving UFW and Docker issues.

UFW is a popular iptables front end on Ubuntu that makes it easy to manage firewall rules. But when Docker is installed, Docker bypass the UFW rules and the published ports can be accessed from outside.

The issue is:

1. UFW is enabled on a server that provides external services, and all incoming connections that are not allowed are blocked by default.
2. Run a Docker container on the server and use the-p option to publish ports for that container on all IP addresses.For example:docker run -d --name httpd -p 0.0.0.0:8080:80 httpd:alpine, this command will run an httpd service and publish port 80 of the container to port 8080 of the server.
3. UFW will not block all external requests to visit port 8080. Even the commandufw deny 8080 will not prevent external access to this port.
4. This problem is actually quite serious, which means that a port that was originally intended to provide services internally is exposed to the public network.

Searching for "ufw docker" on the web can find a lot of discussion:

• moby/moby#4737
• https://forums.docker.com/t/running-multiple-docker-containers-with-ufw-and-iptables-false/8953
• https://www.techrepublic.com/article/how-to-fix-the-docker-and-ufw-security-flaw/
• https://blog.viktorpetersson.com/2014/11/03/the-dangers-of-ufw-docker.html
• https://askubuntu.com/questions/652556/uncomplicated-firewall-ufw-is-not-blocking-anything-when-using-docker
• https://chjdev.com/2016/06/08/docker-ufw/
• https://askubuntu.com/questions/652556/uncomplicated-firewall-ufw-is-not-blocking-anything-when-using-docker
• https://my.oschina.net/abcfy2/blog/539485
• https://www.v2ex.com/amp/t/466666
• https://blog.36web.rocks/2016/07/08/docker-behind-ufw.html
• ...

Almost all of these solutions are similar. It requires to disable docker's iptables function first, but this also means that we give up docker's network management function. This causes containers will not be able to access the external network. It is also mentioned in some articles that you can manually add some rules in the UFW configuration file, such as-A POSTROUTING ! -o docker0 -s 172.17.0.0/16 -j MASQUERADE. But this only allows containers that belong to network172.17.0.0/16 can access outside. If we create a new docker network, we must manually add such similar iptables rules for the new network.

The solutions that we can find on internet are very similar and not elegant, I hope a new solution can:

• Don't need to disable Docker's iptables and let Docker to manage it's network.We don't need to manually maintain iptables rules for any new Docker networks, and avoid potential side effects after disabling iptables in Docker.
• The public network cannot access ports that published by Docker. Even if the port is published on all IP addresses using an option like-p 8080:80. Containers and internal networks can visit each other normally.Although it is possible to have Docker publish a container's port to the server's private IP address, the port will not be accessed on the public network. But, this server may have multiple private IP addresses, and these private IP addresses may also change.
• In a very convenient way to allow/deny public networks to access container ports without additional software and extra configurations. Just like using commandufw allow 8080 to allow external access port 8080, then using commandufw delete allow 8080 to deny public networks visit port 8080.

If you have modified your server according to the current solution that we find on the internet, please rollback these changes first, including:

• Enable Docker's iptables feature.Remove all changes like--iptables=false , including configuration file/etc/docker/daemon.json.
• UFW's default FORWARD rule changes back to the default DROP instead of ACCEPT.
• Remove the rules related to the Docker network in the UFW configuration file/etc/ufw/after.rules.
• If you have modified Docker configuration files, restart Docker first. We will modify the UFW configuration later and we can restart it then.

This solution needs to modify only one UFW configuration file, all Docker configurations and options remain the default.

Modify the UFW configuration file/etc/ufw/after.rules and add the following rules at the end of the file:

# BEGIN UFW AND DOCKER*filter:ufw-user-forward - [0:0]:ufw-docker-logging-deny - [0:0]:DOCKER-USER - [0:0]-A DOCKER-USER -j ufw-user-forward-A DOCKER-USER -j RETURN -s 10.0.0.0/8-A DOCKER-USER -j RETURN -s 172.16.0.0/12-A DOCKER-USER -j RETURN -s 192.168.0.0/16-A DOCKER-USER -p udp -m udp --sport 53 --dport 1024:65535 -j RETURN-A DOCKER-USER -j ufw-docker-logging-deny -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 192.168.0.0/16-A DOCKER-USER -j ufw-docker-logging-deny -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 10.0.0.0/8-A DOCKER-USER -j ufw-docker-logging-deny -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 172.16.0.0/12-A DOCKER-USER -j ufw-docker-logging-deny -p udp -m udp --dport 0:32767 -d 192.168.0.0/16-A DOCKER-USER -j ufw-docker-logging-deny -p udp -m udp --dport 0:32767 -d 10.0.0.0/8-A DOCKER-USER -j ufw-docker-logging-deny -p udp -m udp --dport 0:32767 -d 172.16.0.0/12-A DOCKER-USER -j RETURN-A ufw-docker-logging-deny -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW DOCKER BLOCK] "-A ufw-docker-logging-deny -j DROPCOMMIT# END UFW AND DOCKER

Using commandsudo systemctl restart ufw orsudo ufw reload to restart UFW after changing the file. Now the public network can't access any published docker ports, the container and the private network can visit each other normally, and the containers can also access the external network from inside.There may be some unknown reasons cause the UFW rules will not take effect after restart UFW, please reboot servers.

If you want to allow public networks to access the services provided by the Docker container, for example, the service port of a container is80. Run the following command to allow the public networks to access this service:

ufw route allow proto tcp from any to any port 80

This allows the public network to access all published ports whose container port is80.

Note: If we publish a port by using option-p 8080:80, we should use the container port80, not the host port8080.

If there are multiple containers with a service port of80, but we only want the external network to access a certain container. For example, if the private address of the container is172.17.0.2, use the following command:

ufw route allow proto tcp from any to 172.17.0.2 port 80

If the network protocol of a service is UDP, for example a DNS service, you can use the following command to allow the external network to access all published DNS services:

ufw route allow proto udp from any to any port 53

Similarly, if only for a specific container, such as IP address172.17.0.2:

ufw route allow proto udp from any to 172.17.0.2 port 53

The following rules allow the private networks to be able to visit each other. Normally, private networks are more trusted than public networks.

-A DOCKER-USER -j RETURN -s 10.0.0.0/8-A DOCKER-USER -j RETURN -s 172.16.0.0/12-A DOCKER-USER -j RETURN -s 192.168.0.0/16

The following rules allow UFW to manage whether the public networks are allowed to visit the services provided by the Docker container. So that we can manage all firewall rules in one place.

-A DOCKER-USER -j ufw-user-forward

For example, we want to block all outgoing connections from inside a container whose IP address is 172.17.0.9 which means to block this container to access internet or external networks. Using the following command:

ufw route deny from 172.17.0.9 to any

The following rules block connection requests initiated by all public networks, but allow internal networks to access external networks. For TCP protocol, it prevents from actively establishing a TCP connection from public networks. For UDP protocol, all accesses to ports which is less then 32767 are blocked. Why is this port? Since the UDP protocol is stateless, it is not possible to block the handshake signal that initiates the connection request as TCP does. For GNU/Linux we can find the local port range in the file/proc/sys/net/ipv4/ip_local_port_range. The default range is32768 60999. When accessing a UDP protocol service from a running container, the local port will be randomly selected one from the port range, and the server will return the data to this random port. Therefore, we can assume that the listening port of the UDP protocol inside all containers are less then32768. This is the reason that we don't want public networks to access the UDP ports that less then32768.

-A DOCKER-USER -j DROP -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 192.168.0.0/16-A DOCKER-USER -j DROP -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 10.0.0.0/8-A DOCKER-USER -j DROP -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 172.16.0.0/12-A DOCKER-USER -j DROP -p udp -m udp --dport 0:32767 -d 192.168.0.0/16-A DOCKER-USER -j DROP -p udp -m udp --dport 0:32767 -d 10.0.0.0/8-A DOCKER-USER -j DROP -p udp -m udp --dport 0:32767 -d 172.16.0.0/12-A DOCKER-USER -j RETURN

If a docker container doesn't follow the OS's settings when receiving data, that is to say, the minimal port number less than32768. For example, we have a Dnsmasq container. The minimal port number that Dnsmasq uses for receiving data is1024. We can use the following command to allow a bigger port range used for receiving DNS packages.

ufw route allow proto udp from any port 53 to any port 1024:65535

Because DNS is a very common service, so there is already a firewall rule to allow a bigger port range to receive DNS packages.

Pro:

Easy to use and understand, supports older versions of Ubuntu.

For example, to allow the public to visit a published port whose container port is8080, use the command:

ufw allow 8080

Con:

It not only exposes ports of containers but also exposes ports of the host.

For example, if a service is running on the host, and the port is8080. The commandufw allow 8080 allows the public network to visit the service and all published ports whose containers' port is8080. But we just want to expose the service running on the host, or just the service running inside containers, not the both.

To avoid this problem, we may need to use a command similar to the following for all containers:

ufw allow proto tcp from any to 172.16.0.3 port 8080

Pro:

Cannot expose services running on hosts and containers at the same time by the same command.

For example, if we want to publish the port8080 of containers, use the following command:

ufw route allow 8080

The public network can access all published ports whose container ports are8080.

But the port8080 of the host is still not be accessed by the public network. If we want to do so, execute the following command to allow the public access the port on the host separately:

ufw allow 8080

Con:

Doesn't support older versions of Ubuntu, and the command is a bit more complicated. But you can use my script.

If we are using an older version of Ubuntu, we can useufw-user-input chain. But be careful to avoid exposing services that should not be exposed

If we are using a newer version of Ubuntu which is supportufw route sub-command, we'd better useufw-user-forward chain, and useufw route command to manage firewall rules for containers.

This script also supports Docker Swarm mode.

Downloadufw-docker script

sudo wget -O /usr/local/bin/ufw-docker \  https://github.com/chaifeng/ufw-docker/raw/master/ufw-dockersudo chmod +x /usr/local/bin/ufw-docker

Then using the following command to modify theafter.rules file ofufw

ufw-docker install

This command does the following things:

• Back up the file/etc/ufw/after.rules
• Append the rules of UFW and Docker at the end of the file

We can only use this script on manager nodes to manage firewall rules when using in Swarm mode.

• Modifying allafter.rules files on all nodes, including managers and workers
• Deploying this script on manager nodes

Running in Docker Swarm mode, this script will add a global serviceufw-docker-agent. The imagechaifeng/ufw-docker-agent is also automatically built from this project.

Show help

ufw-docker help

Check the installation of firewall rules in UFW configurations

ufw-docker check

Update UFW configurations, add the necessary firewall rules

ufw-docker install

Show the current firewall allowed forward rules

ufw-docker status

List all firewall rules related to containerhttpd

ufw-docker list httpd

Expose the port80 of the containerhttpd

ufw-docker allow httpd 80

Expose the443 port of the containerhttpd and the protocol istcp

ufw-docker allow httpd 443/tcp

Expose the443 port of the containerhttpd and the protocol istcp and the network isfoobar-external-network when the containerhttpd is attached to multiple networks

ufw-docker allow httpd 443/tcp foobar-external-network

Expose all published ports of the containerhttpd

ufw-docker allow httpd

Remove all rules related to the containerhttpd

ufw-docker delete allow httpd

Remove the rule which port is443 and protocol istcp for the containerhttpd

ufw-docker delete allow httpd 443/tcp

Expose the port80 of the serviceweb

docker service create --name web --publish 8080:80 httpd:alpineufw-docker service allow web 80# orufw-docker service allow web 80/tcp

Remove rules from all nodes related to the serviceweb

ufw-docker service delete allow web

We useVagrant to set up a local testing environment.

Run the following command to create 1 master node and 2 worker nodes

vagrant up

Log into the master node

vagrant ssh master

After logging in, create aweb service

docker service create --name web --publish 8080:80 httpd:alpine

We shouldn't visit thisweb service from our host

curl -v http://192.168.56.131:8080

On the master node, run the command to allow the public access port80 of theweb service.

sudo ufw-docker service allow web 80

We can access theweb service from our host now

curl "http://192.168.56.13{0,1,2}:8080"

• What is the best practice of docker + ufw under Ubuntu - Stack Overflow
• docker and ufw serious problems · Issue #4737 · moby/moby

请直接看解决 UFW 和 Docker 的问题。

UFW 是 Ubuntu 上很流行的一个 iptables 前端，可以非常方便的管理防火墙的规则。但是当安装了 Docker，UFW 无法管理 Docker 发布出来的端口了。

具体现象是：

1. 在一个对外提供服务的服务器上启用了 UFW，并且默认阻止所有未被允许的传入连接。
2. 运行了一个 Docker 容器，并且使用-p 选项来把该容器的某个端口发布到服务器的所有 IP 地址上。比如：docker run -d --name httpd -p 0.0.0.0:8080:80 httpd:alpine 将会运行一个 httpd 服务，并且将容器的80 端口发布到服务器的8080 端口上。
3. UFW 将不会阻止所有对8080 端口访问的请求，用命令ufw deny 8080 也无法阻止外部访问这个端口。

这个问题其实挺严重的，这意味着本来只是为了在内部提供服务的一个端口被暴露在公共网络上。

在网络上搜索 "ufw docker" 可以发现很多的讨论：

• moby/moby#4737
• https://forums.docker.com/t/running-multiple-docker-containers-with-ufw-and-iptables-false/8953
• https://www.techrepublic.com/article/how-to-fix-the-docker-and-ufw-security-flaw/
• https://blog.viktorpetersson.com/2014/11/03/the-dangers-of-ufw-docker.html
• https://askubuntu.com/questions/652556/uncomplicated-firewall-ufw-is-not-blocking-anything-when-using-docker
• https://chjdev.com/2016/06/08/docker-ufw/
• https://askubuntu.com/questions/652556/uncomplicated-firewall-ufw-is-not-blocking-anything-when-using-docker
• https://my.oschina.net/abcfy2/blog/539485
• https://www.v2ex.com/amp/t/466666
• https://blog.36web.rocks/2016/07/08/docker-behind-ufw.html
• ...

基本上可以找到的解决办法就是首先禁用 docker 的 iptables 功能，但这也意味着放弃了 docker 的网络管理功能，很典型的现象就是容器将无法访问外部网络。在有的文章中也提到了可以在 UFW 的配置文件中手工添加一条规则，比如-A POSTROUTING ! -o docker0 -s 172.17.0.0/16 -j MASQUERADE。但这也只是允许了172.17.0.0/16 这个网络。如果有了新增的网络，我们也必须手工再为新增的网络添加这样类似的 iptables 规则。

目前网络上的解决方案都非常类似，而且也不优雅，我希望一个新的解决方案可以：

1. 不要禁用 Docker 的 iptables，像往常一样由 Docker 来管理自己的网络。这样有任何新增的 Docker 网络时都无需手工维护 iptables 规则，也避免了在 Docker 中禁用 iptables 之后可能带来的副作用。
2. 公共网络不可以访问 Docker 发布出来的端口，即使是使用类似-p 0.0.0.0:8080:80 的选项把端口发布在所有的 IP 地址上。容器之间、内部网络之间都可以正常互相访问，只有公共网络不可以访问。虽然可以让 Docker 把容器的某一个端口映射到服务器的私有 IP 地址上，这样公共网络上将不会访问到这个端口。但是这个服务器可能有多个私有 IP 地址，这些私有 IP 地址可能也会发生变化。
3. 可以很方便的允许公共网络直接访问某个容器的端口，而无需额外的软件和配置。就像是用ufw allow 8080 这样允许外部访问 8080 端口，然后用ufw delete allow 8080 就不再允许外部访问。

如果已经按照目前网络上搜索到解决方案修改过了，请先修改回来，包括：

1. 启用 Docker 的 iptables 功能，删除所有类似--iptables=false 的修改，包括/etc/docker/daemon.json 配置文件。
2. UFW 的默认FORWARD 规则改回默认的DROP，而非ACCEPT。
3. 删除 UFW 配置文件/etc/ufw/after.rules 中与 Docker 网络相关的规则。
4. 如果修改了 Docker 相关的配置文件，重启 Docker。稍后还要修改 UFW 的配置，可以一并重启。

目前新的解决方案只需要修改一个 UFW 配置文件即可，Docker 的所有配置和选项都保持默认。

修改 UFW 的配置文件/etc/ufw/after.rules，在最后添加上如下规则：

# BEGIN UFW AND DOCKER*filter:ufw-user-forward - [0:0]:ufw-docker-logging-deny - [0:0]:DOCKER-USER - [0:0]-A DOCKER-USER -j ufw-user-forward-A DOCKER-USER -j RETURN -s 10.0.0.0/8-A DOCKER-USER -j RETURN -s 172.16.0.0/12-A DOCKER-USER -j RETURN -s 192.168.0.0/16-A DOCKER-USER -p udp -m udp --sport 53 --dport 1024:65535 -j RETURN-A DOCKER-USER -j ufw-docker-logging-deny -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 192.168.0.0/16-A DOCKER-USER -j ufw-docker-logging-deny -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 10.0.0.0/8-A DOCKER-USER -j ufw-docker-logging-deny -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 172.16.0.0/12-A DOCKER-USER -j ufw-docker-logging-deny -p udp -m udp --dport 0:32767 -d 192.168.0.0/16-A DOCKER-USER -j ufw-docker-logging-deny -p udp -m udp --dport 0:32767 -d 10.0.0.0/8-A DOCKER-USER -j ufw-docker-logging-deny -p udp -m udp --dport 0:32767 -d 172.16.0.0/12-A DOCKER-USER -j RETURN-A ufw-docker-logging-deny -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW DOCKER BLOCK] "-A ufw-docker-logging-deny -j DROPCOMMIT# END UFW AND DOCKER

然后重启 UFW，sudo systemctl restart ufw。现在外部就已经无法访问 Docker 发布出来的任何端口了，但是容器内部以及私有网络地址上可以正常互相访问，而且容器也可以正常访问外部的网络。可能由于某些未知原因，重启 UFW 之后规则也无法生效，请重启服务器。

如果希望允许外部网络访问 Docker 容器提供的服务，比如有一个容器的服务端口是80。那就可以用以下命令来允许外部网络访问这个服务：

ufw route allow proto tcp from any to any port 80

这个命令会允许外部网络访问所有用 Docker 发布出来的并且内部服务端口为80 的所有服务。

请注意，这个端口80 是容器的端口，而非使用-p 0.0.0.0:8080:80 选项发布在服务器上的8080 端口。

如果有多个容器的服务端口为 80，但只希望外部网络访问某个特定的容器。比如该容器的私有地址为172.17.0.2，就用类似下面的命令：

ufw route allow proto tcp from any to 172.17.0.2 port 80

如果一个容器的服务是 UDP 协议，假如是 DNS 服务，可以用下面的命令来允许外部网络访问所有发布出来的 DNS 服务：

ufw route allow proto udp from any to any port 53

同样的，如果只针对一个特定的容器，比如 IP 地址为172.17.0.2：

ufw route allow proto udp from any to 172.17.0.2 port 53

在新增的这段规则中，下面这段规则是为了让私有网络地址可以互相访问。通常情况下，私有网络是比公共网络更信任的。

-A DOCKER-USER -j RETURN -s 10.0.0.0/8-A DOCKER-USER -j RETURN -s 172.16.0.0/12-A DOCKER-USER -j RETURN -s 192.168.0.0/16

下面的规则是为了可以用 UFW 来管理外部网络是否允许访问 Docker 容器提供的服务，这样我们就可以在一个地方来管理防火墙的规则了。

-A DOCKER-USER -j ufw-user-forward

例如，我们要阻止一个 IP 地址为 172.17.0.9 的容器内的所有对外连接，也就是阻止该容器访问外部网络，使用下列命令

ufw route deny from 172.17.0.9 to any

下面的规则阻止了所有外部网络发起的连接请求，但是允许内部网络访问外部网络。对于 TCP 协议，是阻止了从外部网络主动建立 TCP 连接。对于 UDP，是阻止了所有小余端口32767 的访问。为什么是这个端口的？由于 UDP 协议是无状态的，无法像 TCP 那样阻止发起建立连接请求的握手信号。在 GNU/Linux 上查看文件/proc/sys/net/ipv4/ip_local_port_range 可以看到发出 TCP/UDP 数据后，本地源端口的范围，默认为32768 60999。当从一个运行的容器对外访问一个 UDP 协议的服务时，本地端口将会从这个端口范围里面随机选择一个，服务器将会把数据返回到这个随机端口上。所以，我们可以假定所有容器内部的 UDP 协议的监听端口都小余32768，不允许外部网络主动连接小余32768 的 UDP 端口。

-A DOCKER-USER -j DROP -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 192.168.0.0/16-A DOCKER-USER -j DROP -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 10.0.0.0/8-A DOCKER-USER -j DROP -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 172.16.0.0/12-A DOCKER-USER -j DROP -p udp -m udp --dport 0:32767 -d 192.168.0.0/16-A DOCKER-USER -j DROP -p udp -m udp --dport 0:32767 -d 10.0.0.0/8-A DOCKER-USER -j DROP -p udp -m udp --dport 0:32767 -d 172.16.0.0/12-A DOCKER-USER -j RETURN

如果一个容器在接受数据的时候，端口号没有遵循操作系统的设定，也就是说最小端口号要小余32768。比如运行了一个 Dnsmasq 的容器，Dnsmasq 用于接受数据的最小端口号默认是1024。那可以用下面的命令来允许 Dnsmasq 这个容器使用一个更大的端口范围来接受数据。

ufw route allow proto udp from any port 53 to any port 1024:65535

因为 DNS 是一个非常常见的服务，所以已经有一条规则用于允许使用一个更大的端口范围来接受 DNS 数据包

优点：

使用的 UFW 命令比较简单，也比较容易理解，而且也支持老版本的 Ubuntu

比如，允许公众网络访问一个已经发布出来的容器端口8080，使用命令：

ufw allow 8080

缺点：

不仅仅是暴露了已经发布的容器端口，也暴露了主机上的端口。

比如，如果在主机上运行了一个端口为8080 的服务。命令ufw allow 8080 允许了公共网络访问这个服务，也允许了访问所有已经发布的容器端口为8080 的服务。但是我们可能只是希望保留主机上的这个服务，或者是运行在容器里面的服务，而不是两个同时暴露。

为了避免这个问题，我们可能需要使用类似下面的命令来管理已经发布的容器端口：

ufw allow proto tcp from any to 172.16.0.3 port 8080

优点：

不会因为同一条命令而同时暴露主机和容器里面的服务。

比如，如果我们希望暴露所有容器端口为8080 的服务，使用下面的命令：

ufw route allow 8080

现在公共网络可以访问所有容器端口为8080 的已经发布的服务，但是运行在主机上的8080 服务仍然不会被公开。如果我们希望公开主机上的8080 端口，可以执行下面的命令：

ufw allow 8080

缺点：

不支持老版本的 Ubuntu，而且命令的使用上可能也会比较复杂。

如果我们正在使用老版本的 Ubuntu，我们可以使用ufw-user-input。但是要小心避免把不该暴露的服务暴露出去。

如果正在使用支持ufw route 命令的新版本的 Ubuntu，我们最好使用ufw-user-forward，并且使用ufw route 来管理与容器相关的防火墙规则。

现在这个脚本也支持 Docker Swarm。

下载ufw-docker 脚本

sudo wget -O /usr/local/bin/ufw-docker \  https://github.com/chaifeng/ufw-docker/raw/master/ufw-dockerchmod +x /usr/local/bin/ufw-docker

使用下列命令来修改 ufw 的after.rules 文件

ufw-docker install

这个命令做了以下事情：

• 备份文件/etc/ufw/after.rules
• 把 UFW 和 Docker 的相关规则添加到文件after.rules 的末尾

仅仅可以在管理节点上使用ufw-docker 这个脚本来管理防火墙规则。

• 在所有的节点上修改after.rules 这个文件，包括管理节点和工作节点
• 在管理节点上部署这个脚本

运行在 Docker Swarm 模式下，这个脚本将会创建一个全局服务ufw-docker-agent。这个镜像chaifeng/ufw-docker-agent 是由本项目自动构建的。

显示帮助

ufw-docker help

检查 UFW 配置文件中防火墙规则的安装

ufw-docker check

更新 UFW 的配置文件，添加必要的防火墙规则

ufw-docker install

显示当前防火墙允许的转发规则

ufw-docker status

列出所有和容器httpd 相关的防火墙规则

ufw-docker list httpd

暴露容器httpd 的80 端口

ufw-docker allow httpd 80

暴露容器httpd 的443 端口，且协议为tcp

ufw-docker allow httpd 443/tcp

如果容器httpd 绑定到多个网络上，暴露其443 端口，协议为tcp，网络为foobar-external-network

ufw-docker allow httpd 443/tcp foobar-external-network

把容器httpd 的所有映射端口都暴露出来

ufw-docker allow httpd

删除所有和容器httpd 相关的防火墙规则

ufw-docker delete allow httpd

删除容器httpd 的tcp 端口443 的规则

ufw-docker delete allow httpd 443/tcp

暴露服务web 的80 端口

docker service create --name web --publish 8080:80 httpd:alpineufw-docker service allow web 80# 或者ufw-docker service allow web 80/tcp

删除与服务web 相关的规则

ufw-docker service delete allow web

我们使用Vagrant 来创建一个本地的测试环境。

运行下面的命令来创建 1 个 master 节点和 2 个 workder 节点

vagrant up

登录到 master 节点

vagrant ssh master

登录后，创建web 服务

docker service create --name web --publish 8080:80 httpd:alpine

我们应该无法从我们的主机上访问这个web 服务

curl -v http://192.168.56.131:8080

在 master 节点上，运行下面的命令来允许公共访问web 服务端80 端口。

sudo ufw-docker service allow web 80

现在我们可以在我们的主机上访问这个web 服务了

curl "http://192.168.56.13{0,1,2}:8080"

• What is the best practice of docker + ufw under Ubuntu - Stack Overflow
• docker and ufw serious problems · Issue #4737 · moby/moby