wassereimer

Yes homeserver-diagnostics-20230524-1739.zip

And while trying to reboot the last time it wasn't a clean reboot. Unraid generated diagnostics. There Unraid had multiple entrys with May 24 17:40:16 HomeServer emhttpd: Unmounting disks... May 24 17:40:16 HomeServer emhttpd: shcmd (1275): /usr/sbin/zpool export ssd May 24 17:40:16 HomeServer root: cannot unmount '/var/lib/docker/zfs/graph/53bcad0d4b8bd8f9ecdfbdab5a3e843f664a98591a6f57b5836007dd8eceb0d7-init': unmount failed

I dont have any docker images or containers but still have one in unraid

Nothing works at the moment with docker. Is there a way to fix this? Or to completely reset docker? (except the volumes if possible - but i have backups if really needed)

And if i want to do docker-compose up, i now get failed to register layer: exit status 2: "/usr/sbin/zfs fs snapshot ssd/System/b22b6c868df6ce04c55ffda2784887209f9129d6bad85a33dcb6523094c8fa82@749664689" => cannot open 'ssd/System/b22b6c868df6ce04c55ffda2784887209f9129d6bad85a33dcb6523094c8fa82': dataset does not exist usage: snapshot [-r] [-o property=value] ... <filesystem|volume>@<snap> ... For the property list, run: zfs set|get For the delegated permission list, run: zfs allow|unallow

In the unraid UI i just get Execution error Server error When i use docker compose i get the error.

Sorry, here they are! homeserver-diagnostics-20230524-1812.zip

Hi, i get the following error: Error response from daemon: container 9dd69bd732f0f6e4bfd7787f5ef5cc18941253a19c2aee423faa5bcc2d8d480b: driver "zfs" failed to remove root filesystem: exit status 1: "/usr/sbin/zfs fs destroy -r ssd/System/53bcad0d4b8bd8f9ecdfbdab5a3e843f664a98591a6f57b5836007dd8eceb0d7" => cannot open 'ssd/System/53bcad0d4b8bd8f9ecdfbdab5a3e843f664a98591a6f57b5836007dd8eceb0d7': dataset does not exist Im on Unraid Version 6.12.0-rc6 and use the zfs filesystem. Best regards

Hi, just three things: - The Link in "Tab Position (see HERE)" is broken - Would be great to have a responsive option instead of setting width and height. - Thank you for the plugin

Did you had time to look into the data?

Of course. Thank you for looking into it. If I change the "IPv4/IPv6 address assignment" to "Automatic", the br1 Network is correctly created and visible in the routing table. If set to none, that doesn't happen. Even after setting everything in the Docker Settings and enabling the Service. homeserver-diagnostics-20230418-1850.zip

Yeah. Tested it further and it doesn't work. I'm also on 6.12 (rc3). Did you create a bug report if you think it is one? I don't know if it would work in a stable version, because I'm new to Unraid and started with 6.12 because of zfs stuff.

I found something. You write "Assign manually the "old" assignments to the new dedicated interface" but you didn't do that. Look at the ipv6 Gateway at br0 and br1. And it works for me if I don't enable the ipv6 custom network on br1, but just ipv4. Then Unraid creates the br1 macvlan network in docker (but you can't see it in the routing table). So there must be something wrong with taking the "old" assignments from br0.

@insomnia417 said (from deepl): This is not a perfect solution, I tossed 2 weeks, was bored by the crash, and now have downgraded back to 6.11.5, waiting for the official kernel to see if the macvlan bug will be fixed

Same problem for me.