Bug: ERROR no iptables supported found

[ChzWheel]

Is this urgent?

No

Host OS

DSM 7.2.1 Update 5

CPU arch

x86_64

VPN service provider

AirVPN

What are you using to run the container

docker-compose

What is the version of Gluetun

2024-05-02T08:16:52.183Z (commit e0a977c)

What's the problem 🤔

iptables error after trying to build docker container.

I saw bug #2260 had been closed with a successful fix, but I seem to still have issues. I attempted running older versions (v3.38) but came across a different error about netip.parseprefix

I know there is not a minimum of 10 lines of logs, but I'm not sure what else I can add since I only get the same 5 lines repeated.

Share your logs (at least 10 lines)

INFO [routing] default route found: interface eth0, gateway 172.20.0.1, assigned IP 172.20.0.7 and family v4
INFO [routing] local ethernet link found: eth0
INFO [routing] local ipnet found: 172.20.0.0/16
ERROR no iptables supported found: errors encountered are: iptables-nft: iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument (exit status 4); iptables: iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument (exit status 4)
INFO Shutdown successful

Share your configuration

gluetun:
    image: qmcgaw/gluetun:latest
    cap_add:
      - NET_ADMIN
    ports:
      - 8888:8888/tcp
      - 8388:8388/tcp
      - 8388:8388/udp
      - 8090:8090/tcp
      - 9696:9696/tcp
    environment:
      - VPN_SERVICE_PROVIDER=airvpn
      - VPN_TYPE=wireguard
      - WIREGUARD_PRIVATE_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      - WIREGUARD_PRESHARED_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      - SERVER_COUNTRIES=Netherlands
      - WIREGUARD_ADDRESSES=xx.xxx.xxx.xx
      - FIREWALL_OUTBOUND_SUBNETS=172.20.0.0/16,192.168.0.0/24
    network_mode: synobridge
    restart: always

[github-actions]

@qdm12 is more or less the only maintainer of this project and works on it in his free time.
Please:

• do not ask for updates, be patient
• 👍 the issue to show your support instead of commenting
  @qdm12 usually checks issues at least once a week, if this is a new urgent bug,
  revert to an older tagged container image

[Ikzy]

Hey, I have the same problem.

changing the version from :latest to :v3.3.38 works as a temporary solution.

cheers

[ChzWheel]

I had tried switching to v3.38, but ran into an environmental variable error regarding the WIREGAURD_ADDRESSES variable. Since I was getting that issue with the latest version, I didn't troubleshoot much further.

[frepke]

@ChzWheel
Maybe because the typo in WIREGAURD.

[Quentin McGaw]

@ChzWheel @Ikzy docker pull qmcgaw/gluetun and it should do it. That bug was introduced in 4d002a3 and fixed with ef6874f as well as with fb145d6 (TLDR: your kernel is quite old, Synology is to blame for lagging behind)

[github-actions]

Closed issues are NOT monitored, so commenting here is likely to be not seen.
If you think this is still unresolved and have more information to bring, please create another issue.

This is an automated comment setup because @qdm12 is the sole maintainer of this project
which became too popular to monitor issues closed.

[ChzWheel]

It still wasn't working but turns out it was user-error. I was under the impression that using the "latest" tag would automatically pull the latest docker image. But I actually had to go to the list of images where there was an "update available" button. Thanks for the responses.