What's the feature 🧐
While sharing gluetun container network namespace works in most cases and simplify some things(like port forwarding), it has following disadvantages:
- lack of dynamic reconfiguration(e.g. if we add extra container with extra port exposed, we need change gluetun env config to ensure nothing breaks in future, in case we start it via compose or other static configuration files)
- if for some reason gluetun container restarted, other containers becomes broken and need to be restarted
My proposal is to transform\update gluetun to docker network plugin, that will:
- bound to default private docker network and setup gateway network namespace with vpn and firewall configured inside
- watch for containers connected to this network, and read containers labels in order to reconfigure itself:
- for example, "gluetun.expose-port": "8080" label will make gluetun network plugin automatically port-forward it and open in firewall in gateway network namespace
- "gluetun.vpn.forward-upnp": "echo '{{FORWARDED_PORT}}'" - will forward vpn provided upnp port to this container and execute provided cmd command within container
This will open may other useful scenarios, for example multi-vpn, load balancing, etc.
Looking forward for discussion.
Extra information and references
No response
What's the feature 🧐
While sharing gluetun container network namespace works in most cases and simplify some things(like port forwarding), it has following disadvantages:
My proposal is to transform\update gluetun to docker network plugin, that will:
This will open may other useful scenarios, for example multi-vpn, load balancing, etc.
Looking forward for discussion.
Extra information and references
No response