Leaderboard

all gone very quiet after the move. I hope everything is ok @limetech ?

Hi guys. This is a tutorial on how to install Nextcloud as a Docker Container on unRAID. It shows how to set it up using the excellent container by the linuxserver guys. It shows how to use it with a mariaDB database to greatly improve performance. There will be another video in a few days showing how to use with a reverse proxy. Hope its useful.

its ok, I apprecaite the help. I ended up copying the file db.sqllite3 from the bit warden directory on my UD to the appdata folder and overwrote what it had tried to made. I then remapped the docker to point back and my cache drives and now it works fine. I'll do some more testing, but super odd issue.

Not directly related to your problem, but you will get far better performance from your drives by switching the BIOS mode for the SATA controller from IDE/Legacy to instead be AHCI 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] [1002:4390]

Looks like hes on his phone and the links didn't copy/paste

https://lime-technology.com/fo...?do=findComment&comment=676124 Sent from my SM-G935F using Tapatalk

https://lime-technology.com/fo...?do=findComment&comment=676124 Sent from my SM-G935F using Tapatalk

Two things I can think of that might bloat a thinly provisioned image. Has the virtual disk become badly fragmented? Does it use CoW?

@mrcake Weird! What does the docker logs say, is everything running? Just to make sure, have you tried changing the dns on your router? Or are you just testing it in windows? It could help since there probably are some DNSSec settings on the router that could interfere. And lastly are you running any VPN on the windows client?

Yes, it is. When I get a little time I try to keep this updated.

I've never had Apple in the house but I don't think so. Maybe someone else will take that question, or you can research it yourself. unRAID disks are reiserFS, XFS, or btrfs. Unassigned Devices plugin is for connecting drives that are not assigned to the array, hence the name.

You should probably contact LT directly. [email protected]

Was that question to me? You can change the target version in the "Edit" page (where you set up all your parameters). The default container is "diginc/pi-hole:latest" (I think—I am not looking at the unraid screen right now—but the ':latest' part is the tag we want to change). To find the available tags, you go to the docker bug page for the container. That's in an earlier post in this thread, and can be found off the Community Applications listing for any given container. In this case, it is https://hub.docker.com/r/diginc/pi-hole/. So, go to that page and click the "Tags" nav link at the top. Based on the change dates, I figured out that ':latest' must refer to ':debian_v3.3.1' (or newer) and that the version I was running prior to the last update had to be ':debian_v3.3'. Last step is to edit the container, change the ':latest' tag to the ':debian_v3.3' tag and click Apply. The container will reinstall based on the older version. I guess I will follow newer releases and try them every once in while to see if the problem is solved. In the meantime, v3.3 seems to work well enough for me.

Uninstall the advanced button plugin. You will have to though switch the docker page to advanced view, delete the orphaned containers