I have no idea why but my Docker service just isn't working anymore. It is able to start but none of my dockers will start. This started to happen after I restarted Unraid to rebuild a drive that was disabled. I have tried deleting the docker image and starting docker again but I keep getting the same error. 

 

Any idea what I might be able to do?

gurrenlagann-diagnostics-20211029-0035.zip

Nothing obvious. Try 

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications

Did notice disk11 disabled though. Do you know how to deal with that? (Hint: it's not by excluding disk11 from each of your shares as you seem to have done.)

1 hour ago, trurl said:

disk11 disabled though

# 1  Extended offline    Completed: read failure       90%     29877         164512592

I assume you are waiting on a replacement. SInce you have dual parity you still have protection.

3 hours ago, trurl said:

Nothing obvious. Try 

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications

Yea I have tried that and it gives me the same error. Doesn't matter what docker container I try to install it gives me the same error,

 

As for the drive yeah I know how to deal with that. The drive that is in there is a little finicky. it has been able to be build before and there isn't any major smart errors. I'm just going to move the data off of it and then remove it.

Those diagnostics are soon after reboot. Do they include an attempt to create a container?

I can't remember, so here is a diagnostic file where I restarted my Unraid server, removed the docker image file, added Krusader, and then tried to start it and I got the same error.

gurrenlagann-diagnostics-20211029-1327.zip

Is this because I have a data rebuild on going? It stll has about 18 hours to go

 

Rod

it is in docker

I realize I'm replying to an old post, but someone else may find this helpful if they run into the same issue.

 

I ran into this and simply decided to remove and recreate the container. In the process I found that when I installed Grafana, it took over the default Firefox container port (3000). Likely the simplest solution to this issue is to review the docker allocations and assign Firefox to an unused container port. For background, I hadn't noticed this conflict because Firefox is only run when I specifically need it, so Grafana didn't raise any errors when it was installed. I ran into the Firefox error today when I tried to start that container for the first time in weeks.

 

Cheers.

Thank you for replying to the old post!! You saved me a lot of pain.

 

I ran into the same, unfathomably useless error message.   Nothing in the main server logs.  The app/docker that faild had errors in the logs had, wish I took a screenshot but they said something about "window management" IIRC.  Could be wrong on that.

 

Regardless, couldn't find anything that mentioned port conflicts - and ultimately that was my issue as well.  Changed the port in the docker and all is well.

 

If you see this error, check your port settings for conflicts!

 

If you are part of Unraid team, please try to detect this and give a more verbose error (and/or help docker image creators do the same).

 

 

Edited February 14, 20242 yr by lolden

I ran into a similar problem. Not sure why my Unraid SSH port was open.

Specifically, I am running a Gitea container that is utilizing port 22 for SSH. Last night backups were made of my containers and their data, and my backup service automatically starts / stops the containers when the backup tasks are ran. My Gitea container failed to restart after backing up. From what I can see, the SSH port on Unraid itself became active.

 

To validate this, I altered my Gitea containers SSH port from 22 to some random port number. This allowed Gitea to start without issue. When set back to port 22 for SSH it fails with the same error as the original poster.

 

 

With my Gitea container set back to 22 and NOT running, I checked Under Management settings, I confirmed that SSH was set to NO. This was never altered, and I am the only admin for my server.

I ran netstat -napt from the terminal and found:
tcp        0      0 10.253.0.1:22           0.0.0.0:*               LISTEN      21516/sshd: /usr/sb

 

I set SSH to ON, applied, then turned it back off in Unraid management. Confirmed afterwards that the above port was not present when running netstat.

Restarted Gitea without issue. Port 22 is now in use by my Gitea container:

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      5817/docker-proxy 

 

Port 22 is not forwarded on my router, and I didn't see any suspicious login attempts in my syslogs... Could this be a bug?

I too ran into this issue. I read the above posts and although none of them were specifically the answer for my flavor of the issue, they pointed me in the right direction.

I lost a single Docker container after moving my entire home network from 192.0.xx.xx to 10.0.xx.xx. At first everything was working smoothly with the new network. Any hard-coded IP addresses were switched around and all containers came up cleanly. But I needed to restart UnRaid for unrelated reasons and when it came back up all the containers but one came up fine. The one container (binhex-sonarr) was throwing the very unhelpful Execution Error / Server Error dialog.

I ended up getting a clue to the issue by dropping into the UnRaid terminal and running:

docker system events

I watched this as I attempted to start the container and it immediately would throw some kind of network error. (I didn't save the output unfortunately.)

What worked for me was to switch the container to no network and then try to start it again. This time it started cleanly, though obviously it didn't have any networks. Then I switched it back to the previous network settings and restarted again. Everything came up clean.

Hope this helps anyone encountering this dialog in the future!
 

i am getting this on dockers that have already been working.

ollama and whisper.