why about windows

[matthiasdotsh]

You are absolutely right!
I've got it running now, but I think it's just not meant for my use case.

Thanks anyway for this cool project and the quick help!

[kroese]

It says it in the screenshot:

"Perhaps your iptables or kernel needs to be updated.."

Which OS/kernel are you using?

[matthiasdotsh]

Any idea what kernel and iptables versions are needed?

I'm running AlmaLinux9.2

with kernel

$ uname -srm
Linux 5.14.0-284.30.1.el9_2.x86_64 x86_64

and iptables

$ iptables --version
iptables v1.8.8 (nf_tables)

and get the same error...

[kroese]

Try

modprobe  ip_tables 
modprobe  iptable_filter

To load the modules before starting the container.

[matthiasdotsh]

Thanks for your fast reply.

Looks like both are not loaded

$ lsmod | grep ip_tables
$ lsmod | grep ipptable_filter

Unfortunately, I don't have permissions on the relevant host (gitlab shell executor) to change this.

[kroese]

If you enable DHCP mode (see the FAQ) it will not need iptables at all (it switches to a macvtap interface). So that would solve your issue.

However if I understand you correctly, you are trying to run this container in the cloud, which will cause lots of other issues (as I am pretty sure Gitlab will not allow you to use KVM for example), so even if you workaround the network problem you will run into the next problem.

[AlBundy33]

can't initialize iptables table `nat': Table does not exist (do you need to insmod?)

added error message to find this issue when searching