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 6.8.3

Featured Replies

I updated/upgraded to 6.8.3 and I came back to see all my Docker Images are not available, I went to the docker tab and it read "Docker Service Failed to Start". I attached my Diag File because I don't have a clue on how to read the thing. Thank you for any and all help!

aurora-diagnostics-20200311-0650.zip

  • Community Expert

Your docker image is 40G and completely full. It is extremely unlikely you would ever fill even 20G if you had things configured correctly. Also, your domains and system shares are not set to use the cache correctly, and have files on the array.

 

Go to Settings - Docker and disable dockers. Delete the docker image.

Go to Settings - VM Manager and disable VMs.

Leave these disabled until we get those shares configured correctly.

 

 

  • Author

@trurl , how do I configure the shares correctly? NVM I will start over, I deleted all the shares and I know what caused the issue, Sabnzbd

 

 

Edited by Mr.N3rd

  • Community Expert

appdata, domains, and system shares should be cache-prefer, or cache-only. Ideally, you want them all on cache with nothing on the array. Your dockers and VMs will perform better if they are not impacted by the slower parity writes, and your dockers and VMs will keep parity and array disks spinning if you have any of it on the array since these files are always open.

 

Mover will move cache-prefer shares to the array, and these shares are cache-prefer by default, so you must have changed them. But, mover cannot move open files, so before you can get them moved, you must disable docker and VM services as I explained above.

 

Set those shares to cache-prefer and 

15 minutes ago, trurl said:

Go to Settings - Docker and disable dockers. Delete the docker image.

Go to Settings - VM Manager and disable VMs.

Leave these disabled until we get those shares configured correctly.

Then run Mover. Wait for it to complete and post new diagnostics so we can see if anything else needs to be done to get those fixed.

 

Archived

This topic is now archived and is closed to further replies.

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.