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!