January 2, 20242 yr Hello, My cache drive filled up which stopped mo docker containers and caused a error 403 when trying to start them. I emptied my cache and could not restart the containers, same error. and I don't understand why i couldn't restart them as my cache whas empty. so I restarted the server. now, some containers started and others have just error and won't start. any guess? nostromo-diagnostics-20240102-0813.zip
January 2, 20242 yr Community Expert Jan 2 08:09:01 Nostromo rc.docker: tautulli: Error response from daemon: driver failed programming external connectivity on endpoint tautulli (2a1ed25362daedf474e41b28aca6bc5e4b40907dd90269cbcea628e3a322db19): Bind for 0.0.0.0:8181 failed: port is already allocated ... Jan 2 08:09:01 Nostromo rc.docker: binhex-sonarr: Error response from daemon: driver failed programming external connectivity on endpoint binhex-sonarr (bb4072670339492d97227ff3b84abf5227982929f6635ae7dcad8dcf57fcd270): Bind for 0.0.0.0:9897 failed: port is already allocated ... Jan 2 08:09:03 Nostromo rc.docker: binhex-sonarr-coreen: Error response from daemon: driver failed programming external connectivity on endpoint binhex-sonarr-coreen (9ec25242959b4534a2200e8b9a3d8be2f7a9aa49e4ce277910da0ed022dfa223): Bind for 0.0.0.0:9806 failed: port is already allocated Looks like the ports are already in use
January 2, 20242 yr Author nothing has been changed and it worked perfectly before. I checked anyways, that is not it. every port is unique. I tried reinstalling the container, it won't work. I will try docker img delete
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.