(Linux) Docker localhost service refuses to start when connecting with Firewall enabled about desktop-app HOT 8 CLOSED

Custom Firewall exceptions are implemented in v3.8.7.
Now, there is the possibility to exclude addresses or subnets that will be allowed through the firewall when enabled.

Example how to allow communication through exposed ports of docker container:

1. Check the local IP address of the docker interface:
   

2. Add docker interface IP to IVPN Firewall exceptions (the local IP of the default network interface can be added too)
   

from desktop-app.

You can statically exclude the local network interface if you have problems with the "Allow LAN" functionality.
It is not required for solving Docker problems.

from desktop-app.

@stenya I have a different, but kinda similar issue. I am able start/stop Docker containers, but if I start a container with an exposed port, I am unable to connect to it via localhost. Only after running ivpn firewall -lan_allow (which is already enabled) again am I able to connect to my Docker services. This is on Fedora Workstation 35 and Artix Linux.

For anyone else having the above problem:
I've managed to fix it by setting a persistent IP range in /etc/docker/daemon.json like so:

{
  "default-address-pools": [
    {
      "base": "172.17.0.0/16",
      "size": 24
    }
  ],
  "other_settings": "..."
}

And adding 172.17.0.0/16 to IVPN firewall exceptions as described by @stenya above.

This will make sure that all new containers, and the docker daemon itself (the docker0 interface), will have an IP address in that range. Make sure to restart docker daemon for it to take effect.

from desktop-app.

@stenya I have a different, but kinda similar issue. I am able start/stop Docker containers, but if I start a container with an exposed port, I am unable to connect to it via localhost. Only after running ivpn firewall -lan_allow (which is already enabled) again am I able to connect to my Docker services. This is on Fedora Workstation 35 and Artix Linux.

from desktop-app.

@theanonymousexyz Which IVPN Client version do you use?

from desktop-app.

@theanonymousexyz Which IVPN Client version do you use?

@stenya CLI v3.7.0 on both distros. Installed from official channels.

from desktop-app.

@stenya thanks for the fix. I which cases would you exclude the default network interface?

from desktop-app.

Bonus tip: If you want IPv6 connectivity for Docker, make sure to add the fixed IPv6 CIDR from Docker config to IVPN exceptions. In my case, I have the following in /etc/docker/daemon.json:

{
  "ipv6": true,
  "fixed-cidr-v6": "fd00::/80"
}

So I added fd00::/80 to IVPN exceptions.

from desktop-app.