isvein

I have tested it now, it works just as usual, but if you try to use it to move data to an ZFS formatted disk, each folder does not become its own dataset as it does if you create a new share on an zfs drive. All folders and files just gets moved/copied to the pool root

Will the stuff "ZFS Master" plugin do be part of Unraid without the need for the plugin at any time?

After updating dockers, the "Versions" tab on folders still says "update ready", it wont change to "up-to-date" before I refresh the Docker tab. Was like this before 6.12 too, not sure if its by design or a Firefox problem

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.

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.

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

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

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.

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.

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

Is there a way to duplicate this plugin or setup multiple schedules? I have some dockers i want to backup say ones a month and some I want to backup daily. 🤔

So after a lot of searching I tried the following: -create 2 new custom docker networks, vpnwan and vpnlan where vpnlan has the --internal=true flag on -connect the vpn container to both networks and set the LAN side on the vpn to be vpnlan subnet -connect another docker to vpnlan only Result is that I cant access the vpnlan docker from outside and though the vpn I tried the same thing with an proxy network, so I have a reverse proxy server connected to 2 networks, one --internal=true, and I get it to work there, so I know it should work, but I guess there is some routing or something openvpn may change that makes it not to work. edit: got it to work! I had forgot to add the port for the container in the vpn container correct.

Hello So how do you really set up this correct? So I have an Unraid server with div dockers and I have another lab offsite, and I want some containers to be connected to their own isolated network with 1 OpenVPN container connected to the other site and the isolated containers to only be able to talk to the outside though the OpenVPN container. Even it is an option, I don't want the entire Unraid server to be connected to the other site though VPN. I have tried to set up this by setting the container network to "none" and use the parameter "--net=container:OpenVPNContainer", and it works, but the problem with this solution is that if you setup more than one identical container, say an web-server, even if I change the ports on the 2nd one, it wont work, and I think this has to do with that with this solution, the containers share the same IP I know you can setup different docker network types others than the bridged, host and none, and its easy enough to setup an isolated network where each container inside has their own IP on an isolated subnet, and I can get them to talk to each other on the Unraid server, but how to I route them though the VPN container? Do the VPN container need to be connected to 2networks at once? (I read this is possible with newer versions of Docker) I guess there is some routing and config here I miss. If this was multiply physical computers or even VMs, I would have less problems setting this up, I would just put 2NICs on the VPN server. (not sure if I posed this in the right forum )

How can you run 2 of the same container and have both using delugevps as their network? The first instance works fine, but the 2nd seems to use default port and complain about that the port is in use even if I change port in the config. using the parameter "--net=container:binhex-delugevpn" on both

C there is no public beta yet

Hello! My name is Nobody, because I actually read this before buying. And for all who is wondering, where is the beta? when will the beta come out etc etc its been said Soon tm, and Soon tm is not the same as soon! Here is the real definition of Soon tm: "Soon™" does not imply any particular date, time, decade, century, or millennia in the past, present, and certainly not the future. "Soon" shall make no contract or warranty between *company* and the end user. "Soon" will arrive some day, *company* does guarantee that "soon" will be here before the end of time. Maybe. Do not make plans based on "soon" as *company* will not be liable for any misuse, use, or even casual glancing at "soon."" Now ←----------- Very Soon™ -------- Soon (Not Soon™) -------- Soon™ -------- Soon-ish™ --------→ End of Time

Checked the port forwarding and looks like I switched off port 80 access, so turned that on and restarted the container but same happens The folder I think have the right permits Edit: Some certs now is renewed just fine, they are on the same domain and same ip so this is strange Edit2: For 2 of 3certs that was not working, it now suddenly worked to create new ones and delete the old ones, strange

Same thing here I checked the logs and after some time it says "some challenges have failed" Same happens if I after tries to renew manually aka create new cert on same domain. Nothing has changed on my dns end, same dns, same ip, the domains/subdomains should resolve fine as far as I can see. if I use a tool like dnschecker.org to check my cname and a-records, all resolve just fine