Docker App/Contrainer Updates Result in Docker App Failure

[rshuler]

Hi Fellow Unraid(ers),

 

I'm a newbie on Unraid and have been using it for a few months now, and I like what I've been able to do to date with Unraid.  However, I seem to be having an odd issue I would like to see how to resolve.  The issue is that whenever there is a update to one of the Docker Containers, that Container fails to start up after the update, and I have to restore appdata to get that Docker Container working again.

 

So far NextCloud, OpenVPN (now moved to wireguard) and Chevereto have all failed to work after an Docker Container Update, and required restoring appdata to get them working again correctly.

 

Can someone guide me on how to resolve this issue, so that in future my Docker Containers don't fail after updating?

 

Thanks in advance for any help,

Robert

 

 

 

[Squid]

Anything special about the containers?  eg: running their network through another container?

 

What exactly do you mean by fails to start up?

[rshuler]

Hi Squid,

 

Nothing special about the containers.  External App interface is via Nginx Proxy Manager.  Apps are bridged and not networked through another container.

 

When I launch the WebUI or try to access the Container via it website name, I get a gateway failure or so other message about the site not being reachable.

 

Is there some other network setting instead of 'bridge' that should be used?

 

Thanks,

Robert