Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Docker Service failed to start after update to version 7.1.1

Featured Replies

Solved by Squid

  • Author
1 minute ago, Squid said:

Was there any improvement?

Also, besides connect, are you running docker compose plugin or something like Portainer or NextCloudAIO in docker?

3 minutes ago, Squid said:

Was there any improvement?

Also, besides connect, are you running docker compose plugin or something like Portainer or NextCloudAIO in docker?

It still having issue where the webgui unresponsive after 18 - 19 hours

Can you drop to the terminal with a locally attached keyboard & monitor and get the diagnostics from there before you reboot. And this is after Connect was uninstalled? Also, have you tried running a memtest from the boot menu for at least a pass or two if only to rule out memory issues

  • Author
On 5/22/2025 at 11:04 AM, Squid said:

Can you drop to the terminal with a locally attached keyboard & monitor and get the diagnostics from there before you reboot. And this is after Connect was uninstalled? Also, have you tried running a memtest from the boot menu for at least a pass or two if only to rule out memory issues

hi Squid
unable to reply for past few days due to fibre issue

i have run memtest multiple times and pass

attached the new diag file

imrannas-diagnostics-20250525-1645.zip

I also had this error today for the first time since I've been on 7.1.2 and never experienced it before in years.

The containers were all still running, but nothing to see in the frontend with the same error. Even stopping Docker under settings did not help. Stopping the Arrya did not work properly either. Had to use the console afterwards to be able to reboot. Now everything is working again. As soon as I get this error again, I'll let you know.

Edited by thezepter

  • Author
19 minutes ago, thezepter said:

I also had this error today for the first time since I've been on 7.1.2 and never experienced it before in years.

The containers were all still running, but nothing to see in the frontend with the same error. Even stopping Docker under settings did not help. Stopping the Arrya did not work properly either. Had to use the console afterwards to be able to reboot. Now everything is working again. As soon as I get this error again, I'll let you know.

Hi Zepter
the issue resolve when i remove unraid connect plugin

thanks. I have now also removed it for the time being. But it's not a permanent solution. Hope this will be fixed.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.