I just upgraded from 6.11 to 6.12.2 and initially everything was working fine. I have a bunch of dockers I use and they were all working fine. I then decided to upgrade jitsi using docker compose, and it worked fine. after that I was trying to work on my wireguard which hasn't been working for a while and when I tried to stop the array it got stuck unmounting the shares. I had to shutdown the server manually and restart it, after doing that, half my dockers didnt work. they won't start. I tried to downgrade to 6.11, they still wouldn't work. I re-upgraded and thought maybe I'll just reinstall the dockers I have, so I deleted my docker image and used my old templates to reinstall the dockers. the dockers that weren't working before, still won't work (despite me deleting the folders in my apps and trying to do a fresh install). when I look at the server log I get all these docker entering disabled state errors. swag and Nextcloud give a ton of these errors: 

 

nginx: [emerg] no "events" section in configuration

 

not sure where to go from here and I probably made things worse than better. I would appreciate any help. 

Please post the diagnostics.

Thanks a lot. So I ended up deleting my docker and reinstalling all of them. It was a pain but everything was seemingly working until today, when I restarted my resiliosync it doesn't start and gives an execution error. The only thing I did today was use docker compose to install Jitsi. I don't know if this is the problem. I've posted the diagnostics.tower-diagnostics-20230707-2039.zip

On 7/5/2023 at 3:16 AM, JorgeB said:

Please post the diagnostics.

@JorgeB Additional thing, when I tried to delete my resilio-sync and just do a new install, I got this error (in the command execution box of the container install):

 

docker: Error response from daemon: driver failed programming external connectivity on endpoint binhex-resilio-sync (7cdee1e0c80eec8d19376c0bdc99e2d08911e8092cf2587e954b6eccdfcc4461): Error starting userland proxy: listen tcp4 0.0.0.0:8888: bind: address already in use.
 

For that best to ask help in that container support thread/discord, assuming one exists.