QNAP Reverse Proxy Solution for Docker's Lack of IPv6 Support
AI Translation
This post is translated from Chinese into English through AI.View Original
AI-generated summary
The user wants to access a Docker container on their QNAP device from outside their network. However, they only have a public IPv6 address and not a public IPv4 address. They have found that if the Docker network type is set to "host", they can access the container using a DDNS domain name and port. However, if the network type is set to "bridge", they cannot access the container using the same method. This is because the port mapping only supports TCPv4 and the QNAP's container station and virtual switch do not support IPv6 mapping. The solution is to use the QNAP's reverse proxy feature to access the container. They can set up a rule in the reverse proxy settings, specifying the protocol (HTTP), the DDNS domain name, the desired external port, the target protocol (HTTP), the target hostname (either "localhost" or the local device's LAN IP address), and the target port (the LAN port of the device).