I just had this problem also. Took me a while to come across this thread. My nginx docker hung on an update and wouldn't quit. I couldn't force the docker container to stop so I had to do a hard reset/unclean shutdown of Unraid. I've been spinning my wheels for the last hour trying to figure out why I was getting 502 bad gateway messages from nginx. Turns out I had to disable/reenable host access to custom networks.
Just wanted to post this to say, this is still valid and apparently has been going on for quite a while.
docker "host access to custom networks" needs to be reenabled on each unsafe shutdown
-
-
-
-
-
in Prereleases
Posted
I just had this problem also. Took me a while to come across this thread. My nginx docker hung on an update and wouldn't quit. I couldn't force the docker container to stop so I had to do a hard reset/unclean shutdown of Unraid. I've been spinning my wheels for the last hour trying to figure out why I was getting 502 bad gateway messages from nginx. Turns out I had to disable/reenable host access to custom networks.
Just wanted to post this to say, this is still valid and apparently has been going on for quite a while.