I have this weird issue that I don't even know where to begin. Right now I have a Gluetun container running with m3u-editor and m3u-proxy running via Gluetun's network. For whatever reason Gluetun's container restarts at midnight (not sure why), but what's more strange is that m3u-editor will not rebuild successfully until I login to the webui and go to the docker tab. I don't need to take any actions, I just need to navigate to that specific tab and immediately it will start rebuilding and work. It's like a weird Schrodinger's cat situation where the container's behavior changes when being observed. This is annoying because every morning my TV channels are offline and they won't ever come back online until I navigate to the docker tab.

For reference, I'm using the Binhex Gluetun container and for m3u-editor I have the network set to the Gluetun container and have "--restart unless-stopped" in the options. Does anyone know where to start with diagnosing this?

I've been having the same issue too - containers routed through pia-openvpn for me, though. Did you find a fix?

4 hours ago, willm said:

I've been having the same issue too - containers routed through pia-openvpn for me, though. Did you find a fix?

Not a proper solution, no. I found out the restart at midnight was because of the automatic updates I had set up for my containers so I turned those off. Backup App data, Auto updates, and Fix common problems all have an auto update setting that have to be turned off. That doesn't solve the containers not restarting problem, but at least it makes it so they're not going down at midnight. Only minor inconvenience is I have to manually update containers which some may argue is a better anyways.

1. It’s normal that containers networked through other containers only rebuild when restarting the parent container from the docker page.

2. There is a docker container called “ContainerNetwork-AutoFix” that will automatically repair these.