June 11, 20233 yr Hello, Since unraid RC (testing from day1), after a couple of days when dockers updates itself some of them aren't able to start anymore. The only error I get is following: What could be the problem, and where could I start to dig to identify the problem? sekiro-diagnostics-20230611-2208.zip Edited June 11, 20233 yr by TDA
June 11, 20233 yr 4 minutes ago, TDA said: Hello, Since unraid RC (testing from day1), after a couple of days when dockers updates itself some of them aren't able to start anymore. The only error I get is following: What could be the problem, and where could I start to dig to identify the problem? sekiro-diagnostics-20230611-2208.zip 169.21 kB · 0 downloads RC8 has been released now so may be worth checking if it is still annissue in rc8
June 11, 20233 yr Author 4 minutes ago, SimonF said: RC8 has been released now so may be worth checking if it is still annissue in rc8 Will try - but since it's around since 4RC I don't think it will fix it by itself. But I'll install it now and we'll see..
June 11, 20233 yr 15 minutes ago, TDA said: Will try - but since it's around since 4RC I don't think it will fix it by itself. But I'll install it now and we'll see.. If rc8 still has an issue suggest create post in bug reports
June 20, 20233 yr Hi, I have the same error, with the Final version too. Did someone opened a post in Bug Reports ? I wonder why this issue is still present after being in 6.12 since rc4!! Should have been fixed before the Final in my opinion.
June 23, 20233 yr Try the following: Edit the container and make a dummy configuration change so it can be updated. Then start the container.
June 23, 20233 yr version 6.12.1 is totally broken, containers no longer respond, broken dashboard... I'm switching to rc8 to see because I had no problems. Please fix it. Thanks
June 23, 20233 yr 40 minutes ago, Casadream_1 said: version 6.12.1 is totally broken Version 6.12.1 works fine for many users. Please post your diagnostics so we look into your problem.
June 23, 20233 yr This is diag, thanks.osiris-diagnostics-20230623-1804.zip The servers are Dell PowerEdge R320 and R520 Edited June 23, 20233 yr by Casadream_1
July 4, 20233 yr Author I'm still having issue also with 6.12.2. After dockers are updated they aren't able to start anymore. I have to reboot the whole server. Since the popup with the error don't help a lot, is there somewhere I could check logs etc to try to identify the Problem? Also, instead of rebooting the server, I disabled and re enabled Docker. After this, I got another error: I had to restart the whole server again to get it running agian. sekiro-diagnostics-20230704-1722.zip Edited July 4, 20233 yr by TDA Tested and found another problem.
July 6, 20232 yr On 7/4/2023 at 4:23 PM, TDA said: I'm still having issue also with 6.12.2. After dockers are updated they aren't able to start anymore. I have to reboot the whole server. Since the popup with the error don't help a lot, is there somewhere I could check logs etc to try to identify the Problem? Also, instead of rebooting the server, I disabled and re enabled Docker. After this, I got another error: I had to restart the whole server again to get it running agian. sekiro-diagnostics-20230704-1722.zip 169.78 kB · 1 download I'm getting the exact same issue here, had to disable auto-updates because docker was constantly going offline
July 6, 20232 yr @TDA in your diagnostics, I see that "/run" is 100% used. Look for what fills it. Could be related to this.
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.