marcfire93 Posted December 12, 2021 Share Posted December 12, 2021 (edited) Hi, I have 5 docker and none of them will start. I have tried to delete the docker image, starting it again in settings and reinstalling my apps, but I keep getting the same error. None of my containers provide any logs. I am quite inexperienced with docker and Unraid so I might be missing something simple. If you need me to provide any additional information, I will gladly do so. Thank you very much for your help! Edited December 12, 2021 by marcfire93 Quote Link to comment
Squid Posted December 12, 2021 Share Posted December 12, 2021 Post your diagnostics and additionally, pick one of them and do hit "Edit" on it, make a change (any change), then revert that change and then hit Apply. Then post the docker run command that appears. Quote Link to comment
marcfire93 Posted December 12, 2021 Author Share Posted December 12, 2021 15 minutes ago, Squid said: Post your diagnostics and additionally, pick one of them and do hit "Edit" on it, make a change (any change), then revert that change and then hit Apply. Then post the docker run command that appears. nas-diagnostics-20211212-1457.zip Quote Link to comment
Squid Posted December 12, 2021 Share Posted December 12, 2021 unable to retrieve OCI runtime error..... Remove this line from /config/go on the flash drive and reboot curl -o '/usr/bin/runc' -L 'https://github.com/binhex/arch-packages/raw/master/static/x86-64/runc' && chmod +x '/usr/bin/runc' Quote Link to comment
marcfire93 Posted December 12, 2021 Author Share Posted December 12, 2021 11 minutes ago, Squid said: unable to retrieve OCI runtime error..... Remove this line from /config/go on the flash drive and reboot curl -o '/usr/bin/runc' -L 'https://github.com/binhex/arch-packages/raw/master/static/x86-64/runc' && chmod +x '/usr/bin/runc' It worked!! Thank you so much for your help. It's really appreciated 😄👍 Quote Link to comment
sota Posted January 18, 2022 Share Posted January 18, 2022 Would like to note: Same issue for me after a restart after 131 days (trying to sort out another problem.) Immediately had a problem starting any containers. Found this thread, #commented out the noted line (for now), restarted. Containers are starting again. While i'm glad this fixed it, can I get some info as to what/why this happened? AKA, did I miss an announcement someplace? Thanks! Quote Link to comment
Squid Posted January 18, 2022 Share Posted January 18, 2022 @binhex popped out that little command to fix some problems on a previous version of Unraid with a limited set of containers. Once the system was up to date, the command was no longer necessary and caused problems as you saw. FYI if you do ever apply little patches like that, you do have to keep track of them because they may not be necessary in the future. Quote Link to comment
sota Posted January 18, 2022 Share Posted January 18, 2022 (edited) Good to know. I'm guessing I had to have added that at some point? I honestly don't remember ever doing it. Also trying to figure out what could have changed to cause it to be a problem now, as i'm very much an Ain't Broke Don't Fix type of guy... still on 6.7.2 for that reason. Edited January 18, 2022 by sota Quote Link to comment
mhowland24 Posted May 23, 2023 Share Posted May 23, 2023 Similar issue, just noticed a few days ago that swag, qbittorrent, photoprism and some others weren't starting after being stopped and updated. I've attached my diagnostics and would really appreciate someone taking a look when they have a second. Thanks tower-diagnostics-20230522-2047.zip Quote Link to comment
JeremiePlam Posted June 14, 2023 Share Posted June 14, 2023 (edited) Same here Server has been running fine for a couple of days, but if I stop a container and try to start it again, I get "Execution error : Server error" The line from binhex isn't present here /config/go on my flash drive Restarting the whole server fixes this, but constantly restarting isn't ideal unraid-diagnostics-20230614-1054.zip Edited June 14, 2023 by JeremiePlam Quote Link to comment
Bushibot Posted December 20, 2023 Share Posted December 20, 2023 Just started getting this after a update failed on one container but it's impacting multiple. Diag attached. nas-mass-diagnostics-20231220-0133.zip Quote Link to comment
Recommended Posts
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.