March 14Mar 14 Hi!After a reboot of my server a couple of arbitrary Docker containers did not start automatically:I tried to start them from the GUI and got a "Error code 403". So I delete the containers in question and tried to recreate them. But this time I got a "docker: Error response from daemon: Address already in use.". I also tried to stop and start the Docker daemon again with and without a reboot. No luck.The problem is, that I am very sure, that the port is not in use (lsof -i :8088 reports nothing in case of nginx configured on that port)?! And it worked before the reboot without change. What am I doing wrong? Help would be very much appreciated....Thanks a lot!Thorstenunraid-diagnostics-20260314-1737.zip Edited March 14Mar 14 by Tom7320
March 15Mar 15 Community Expert Try recreating the Docker folder as an image instead; in my experience, folders can cause strange issues.https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-fileThen:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applicationsAlso see below if you have any custom docker networks:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks
March 15Mar 15 Author Yes, thanks! That's exactly what I did. It worked, but I wanted to avoid it, since I had to re-install 45+ containers by hand which took me about two hours of clicking around. But at least there was no data loss AFAIK.... ð
March 15Mar 15 Community Expert 26 minutes ago, Tom7320 said:since I had to re-install 45+ containers by handYou should be able to restore them all from CA previous apps with a couple of clicks.
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.