Couldn't load match `comment':No such file or directory

[strandloper]

I'm trying to help my son get set up on an Asustor AS1102T NAS device and have run into problems that we are unable to solve with our limited networking knowledge.

This is the command we're using to create the container

sudo docker run --privileged -d -v /volume1/Docker/Qbittorrentvpn/config/:/config -v /volume1/downloads/:/downloads -e "VPN_ENABLED=yes" -e "VPN_TYPE=openvpn" -e "LAN_NETWORK=192.168.1.0/24" -e "PUID=1001" -e "TZ=Africa/Johannesburg" -e "DEBUG=yes" -p 8080:8080 --restart unless-stopped trigus42/qbittorrentvpn

It seems that iptables is failing to set up the rules and it logs the following for each rule.

iptables v1.8.7 (legacy): Couldn't load match `comment':No such file or directory Try `iptables -h' or 'iptables --help' for more information.

We have enabled debugging and followed through the 03-network.sh file and the log (attached). All seems to be fine except for these iptables failures. From some searching and reading of iptables documentation, it would seem that a possible cause is that the comment extension module is not available with the version of iptables being used. But we have no idea how to try to solve this.

_agitated_boyd_logs.txt

[Trigus42]

The commit 2e9d22f should fix your issue

[TheLurch]

I've just pulled the latest release using sudo docker pull trigus42/qbittorrentvpn then run the same command to create the container as above howeve the behaviour seems the same.

I've attached an update log, I hope that helps shed some light.

_zen_elion_logs (1).txt

[Trigus42]

Can you run docker run --rm -it trigus42/qbittorrentvpn lsmod on the affected host and post the result?
Edit:
Just to be sure, please also run docker run --rm -it trigus42/qbittorrentvpn bash -c "lsmod | grep xt_comment"; echo $? and try to load the module on the host using modprobe xt_comment, then restart the container

[TheLurch]

Here is the result of docker run --rm -it trigus42/qbittorrentvpn lsmod

This is what I am seeing running the other 2 commands:

Just to be clear, I am running these via SSH into the device.

[Trigus42]

There was a problem with the regex. It should now be fixed (bc7ec8e)