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.

Can't start or remove Containers - ZFS Issue?

Featured Replies

Hi Everyone!

I'm sorry if this has been answered somewhere already, but I could not find a solution to my problem.

 

After my Flash drive died, I used a backup to create a new boot drive. After everything seemed to be fine, I realized that some Containers were not running (e.g Nextcloud or Home Assistant). I tried starting them manually, but got the message "Execution error - Image can not be deleted, in use by other container(s)". I looked everywhere but could not find another container that was using the Image so I tried deleting the container in order to recreate it. When I do this, I get another error message "Execution error - Server error". So after this, the container cannot be edited (Option is not available in the context menu), started or deleted. I tried force-updating, which either results in

  • the error message "Configuration not found. Was this container created using this plugin?" or in other cases
  • the error message "Error response from daemon: Conflict. The container name "/Home-Assistant" is already in use by container "af29e894be9aac393302a4f5300f47dd19494ad1aef81ded8b605378c2421ce9". You have to remove (or rename) that container to be able to reuse that name." and an orphanaged image 

 

So I tried to go the manual route using the console:

Quote

root@homelab:~# docker rm Home-Assistant
Error response from daemon: container af29e894be9aac393302a4f5300f47dd19494ad1aef81ded8b605378c2421ce9: driver "zfs" failed to remove root filesystem: exit status 1: "/usr/sbin/zfs fs destroy -r nvme-a-main/system/be484ed42601764f510ac32e29858d139354f98b6f2c2cac213f6bc4f96fea3c" => cannot open 'nvme-a-main/system/be484ed42601764f510ac32e29858d139354f98b6f2c2cac213f6bc4f96fea3c': dataset does not exist

 

This error message finally gave me the feeling, that something went wrong when I converted my cache drive (nvme-a-main) to zfs a couple o f weeks ago. ( I am using a directory instead of an image for docker)

 

To me it seems like there are multiple indipendent problems occuring, the most important beeing some problems with the file system?

 

I'd be very glad for any tip or pointer in the right direction as im now clueless on how to continue.

Should I upload the diagnostics files?

  • 2 weeks later...
  • Author

So I fixed this by changing the docker setting back from directoy to image. Then I redownloaded all images and restored all containers.

Does anyone know of I now have the old images laying some where? Should I delete them?

And should I be concerned by the zfs error?

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.