How can I stop container networks routing through VPN container from resetting?

• gluetun

  374 6,138 9.2 Go

  VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.

I have several containers set up to use a different container as their network. You assign ports to the VPN container and it makes the other containers reachable. It all works very nicely and how I want with one exception. Whenever the VPN container, https://github.com/qdm12/gluetun, restarts, each and every container relying on it for networking loses their configuration. In portainer, a client container would change to network: container container: blank instead of persisting the container name. Any thoughts on this would be helpful and appreciated.

• Moby

  212 67,768 10.0 Go

  The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems

  

This is a long standing issue with Docker itself - if you use container mode networking you need to be very careful with your restart order, and as you've discovered, if the network "parent" container restarts it will affect the networking of any "child" containers. This Github ticket in the Docker repository discusses this in detail.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project