I've tried doing a search, but either I can't find it, or others aren't having the issue...

For a few weeks I've been using the GluetunVPN docker container as the network interface for several other containers. However if the GluetunVPN container gets auto updated, any container that is using that as the network interface do not auto rebuild, unless I open a web browser to the docker tab (at which point they rebuild & all works ok again).

At the moment, I've just turned off auto-updates on the GluetunVPN container, so I can manually update & ensure the other containers are rebuilt as needed, but I'd like it to stay automatic where possible. Am I missing something here that's preventing the auto-rebuild?

Running Unraid V7.1.4

This is the downside of using a docker container as a network essential when gluten updated its changed network keys for the other containers connected to it.

You can get around this with docker compose this way when updates occur to the whole stack the entire stack goes down to maintain the network...

https://bmartino1.weebly.com/guide-dockernetworks.html

8 hours ago, thingie2 said:

Am I missing something here that's preventing the auto-rebuild?

in docker there isnt a real "auto-rebuild", its just what the gui sells you it as, its a full recreation of the container, i.e removing and deploying it.

Try this new container: https://forums.unraid.net/topic/194313-support-containernetwork-autofix-cnaf-auto-fix-vpn-dependent-containers/

Thank you all, I assumed the "child" containers needed rebuilding due to the Gluetun container ID changing (or at least being something similar to that), but thought that I must be missing something, as Unraid sorts it all automatically if I browse to the docker tab, but it would make sense why it doesn't do it otherwise, if it's a frontend fix/workaround, rather than a core functionality.

@strike Thanks for pointing me to that container, that looks to be exactly what I need, so I'll give it a go.