gluetun: can't initialize iptables table?

Au Melbourne works so I suspect the addresses have changed @qdm12

I’m moving from my current docker setup as containers crash all the time so I’ll probably just manually do composer without protainer anyway. I think the issue here was the portainer cannot create / run the new container as root so it cannot get network permissions. There seems to be a lot of chat on portainers side as they need to redo a bunch of work to get to v3.

@winklevos can you try with the terminal just to make sure it works? Let me know if you need help.

I think @HerbM3 is running it with Portainer though.

Quentin,

Did you see the edit in my previous post about @winklevos earlier post?

Please tell me it’s Portainer because I’m running low on ideas 😆

I think Portainer doesn’t support docker-compose 3 which might be needed for NET_ADMIN, although I believe other people are running it with Portainer? Maybe @Frepke do/did you run it with Portainer?

No sorry, I’m running docker-compose.yml -d from the terminal.

But @winklevos wrote in an earlier post:

I'm seeing this error too, here is the complete log. Using docker compose, on a boot2docker image in virtbox.

Ah, I did not and running it with NET_ADMIN seemed to fix my issue indeed. Thanks @qdm12.

Are you guys sure you run the container with NET_ADMIN capabilities? Because it seems very similar to this issue.