isvein

Now v27 is out and same problem, stuck on the backup phase. I remember I had to delete an file before it worked though the terminal but cant remember what file.

Have I understood it correct that what the stuff ZFS Master plugin does will one day be part of unraid wthout need of a plugin?

Same happens here, even if signups and invitations are turned off everywhere. Or is this just a warning about that this 3 variables are overridden by the config.json file? It also complains about that the admin-token is in clear text but I have not managed to successful change this.

Tested the thing with custom docker networks on 192.168.X.0/24 subnet and it seems to work again

true! right after I wrote it there was a new update and after it went well, changing the tag to 26.0.2 worked

Same thing here, followed the guide from @tomwhi and got it to work after a few tries. Then tried to update the tag to 26.0.2 but then got the same php version error. Had to go back to 26.0.1 for it to work, nextcloud gui says Nextcloud Hub 3 (25.0.7) and there is no newer update. Gonna keep the tag at 26.0.1 for now

that I totally understand and that is fine, but it still dont explain why "docker create network test --subnet 192.168.2.0/24 --gateway 192.168.2.1" does not work as expected but "docker create network test --subnet 172.2.0.0/16 --gateway 172.2.0.1" does work. By working I mean I can access the dockers from the lan (in my case thats is 192.168.0.0/24) (aka the network gets routed/not routed correctly. By not stetting a driver they both defaults to bridge, so should work in both cases)

Seems to work again after the update that came today

Same happens here now. Doing the same as you did does not work for me and I cant find any reason why it would skip some dockers that clearly has data in their app-folder

Tried again, following the procedure in this post: Even deleted my old "Docker" share and created an new with the name "docker" Same happens, same errors containers wont work on custom networks created in terminal with "docker create network "name" --subnet "custom-subnet" and then setting fixed ip for the docker(s) Not setting a static ip on container with custom subnet does also NOT work. What does work, is custom docker network created WITHUOUT the --subnet flag so you get an 172.18.0.0/16 subnnet and with no static IP to the container. ------------------ So I checked the settings for both this networks using "docker network inspect "name"" and I see that the 172 subnet gets an gateway in its config but my custom subnet netwrok does NOT get an gateway. But, even creating a network with for example "docker create network "name" --subnet "192.168.2.0/24" --gateway "192.168.2.1"" does not work, the config gets the gateway but the container cant connect So something in the back-end seems to not route things right and/or setup custom subnets correct when docker is on zfs folder ----------- When using the same command for example "docker create network "name" --subnet "192.168.2.0/24" --gateway "192.168.2.1"" when docker is on an btrfs image (still on the zfs-pool) it works Also found out that if you dont use the --gateway flag, the docker network does not list an gateway, but it still works on the brtfs image Just using "docker network create "name" so you get an 172 subnet, does create an gateway in the config tho. -------------- So I cant understand it any different that when the docker is in a folder on zfs, something strange happens with the routing when creating a custom network with custom subnet or that the docker implementation on Unraid is not meant to work with custom networks with custom subnets ----- Edit again: I tried to make an custom subnet of 172.50.0.0/16 and that DOES work 😮 (just to see what would happen if I used the same network class as the auto generated ones) even with custom ip address for the container. So for some reason, docker on my side does NOT like 192.168.X.0/24 subnets when on folder. if this is what it takes, I guess I can change my custom networks scopes

Seems to still be problems with Docker running off folder on zfs If I look in say NginxproxyManager: [app ] [5/18/2023] [7:28:47 AM] [Global ] › ℹ info Manual db configuration already exists, skipping config creation from environment variables [app ] [5/18/2023] [7:28:49 AM] [Migrate ] › ℹ info Current database version: none [app ] [5/18/2023] [7:28:51 AM] [Setup ] › ℹ info Added Certbot plugins certbot-dns-domeneshop~=0.2.8 [app ] [5/18/2023] [7:28:51 AM] [Setup ] › ℹ info Logrotate Timer initialized [app ] [5/18/2023] [7:28:51 AM] [Setup ] › ℹ info Logrotate completed. [app ] [5/18/2023] [7:28:51 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [app ] [5/18/2023] [7:28:51 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [app ] [5/18/2023] [7:28:56 AM] [IP Ranges] › ✖ error getaddrinfo EAI_AGAIN ip-ranges.amazonaws.com [app ] [5/18/2023] [7:28:56 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [app ] [5/18/2023] [7:28:56 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [app ] [5/18/2023] [7:28:56 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [app ] [5/18/2023] [7:28:56 AM] [Global ] › ℹ info Backend PID 437 listening on port 3000 .. I get what looks like an network error. This error does not happen if set to default bridge

aha so it controlls the zfs-arc-ram-cache Thank you! What does the sync-->Always/Disabled refer to?

hello What does the Primary Cache-->All/Metadata/None mean?

I tried that too, starting with a clean docker folder, but same happens with custom networks sadly Difference is that I run 6.12rc5, so maybe its a bug just there. Putted it in the RC5 thread too.

Tried to change my cache to zfs and use docker using folder instead of image today. While docker works fine with the old image file, with folder, custom networks wont work, the dockers seems to have no route even if I tried to create the docker network with and without --gateway "ip" option. Anyone else has tried this? Tried to search but could not find an tread about it. For all I know this may not be zfs related at all, but it worked fine under btrf cache drive Guess I just use the image for now.

So that may be my problem then 😮 I changed my cache to zfs today just because I want to try it, and while dockers work, custom networks wont, its like they dont have a route. If I set an container to use default bridge network, it works. The image I still have works just fine

Hello:) So in Docker settings you can setup btrfs-image, xfs-image or just folder. When and why would you use one over the other? Up to now I just been using btrfs-image on an btrfs cache, but thinking of manybe trying out an zfs-cache and was then thinking of this.

Now it got complicated 😵‍💫 But thanks 😃

Im trying to understand the ZFS lingo: -an Vdev is an set of drives in a given raid array (can be compared to a raid array like raid0,1,5,6 etc) -an ZFS Pool is an logical collection of 1 or more Vdevs that looks like a single point of access to the user -Vdevs are independent even if in a ZFS-Pool, so say 1 Mirror Vdev and 1 stripe Vdev in same ZFS-Pool does not make it equal to raid 10 -if one drive in any Vdev goes down, you loose access to the entire ZFS pool Do I understand that correct?

One "problem" I have with this docker is that even if I have set the timezone correct for my location, its 2hours later Say I set an minecraft server to take backup at 10PM, it takes backup at midnight

Got it to work with MC, its very clean and better than doing all from command line and scripts, but a few things, some that has been mentioned before here: -the docker does not open any game ports, just the AMP web-port so you need to add any game ports you want to the docker config. -AMP uses "instances" and inside 1 instance you run 1 game. So if you just from the main page choose config, this is the AMP config. -To config a game, goto "instances-->select the game-->manage" the top of "main page" should now say "Return to Instances" and everything in this menu is now for that specific game. -Same goes for starting the game server. The instance may say running, but you need to go to manage and from the "Status" click on Start to start the server. At least this is true for Minecraft, not tried anything else yet This last part really confused me because I thought when you start the instance you also start the server, but NOPE! I wonder if this is the problem @ToastedPirate has

True. All my dockers is mapped in /mnt/user/appdata/*

Maybe that is why nextcloud suddenly loaded way faster pictures and stuff, even if my appdata runs only on data ssd in raid1 btrfs 😮

So Im trying to understand the new "exclusive" mode, and by reading about it I have a hard time get it, so I checked my shares as I though that an share that is ONLY on a pool (example the cache pool) should have exclusive on. Found out the system, tmp and VM share was exclusive yes, but my appdata was no So I checked the drives one by one and sure I found "appdata" on one of the drives, but the folder was empty. But this fits the description of how exclusive works, it only cares if the "sharename" (in my example "appdata") is on any other disks in the array or other pools, files or no files. So I removed the "appdata" from the disk, restarted the array, and then "appdata" was on "exclusive yes" But what I still dont get is what it does in practice. I think it has something to do how the share gets mounted, but that is as far as I get 😐

Woop! This fixed the top bar/menu for me. its not cut off on the bottom, was this in different browsers so not sure if it was something in the update that fixed it or an local thing. Dockers still just spins on update and never finishes, but if I click on docker in menu again, updates are shown if any and they update normally so its not a big deal for me.