And the gluetun container is re-created due to a new version, the using container is marked as "unhealthy" but a container restart won't work because the container ID of the gluetun container is changed.
Consider adding an option "deunhealth.recreate.on.unhealthy=true" to resolve this.
If you have a service configured similar to the following:
And the gluetun container is re-created due to a new version, the using container is marked as "unhealthy" but a container restart won't work because the container ID of the gluetun container is changed.
Consider adding an option "deunhealth.recreate.on.unhealthy=true" to resolve this.