SSMI

What container is considered the official? I thought it was the All-In-One because that is what the Nextcloud website seems to recommend. On top of that none of the templates from the apps tab seem to be directly from Nextcloud. If I wanted to switch to the AIO container as long as my docker.img was on something with redundancy (like a two disk cache) it would have similar redundancy to the array and be somewhat protected right? Then I could use the AIO with the data and back locations mapped like the documentation says and things would be relatively reliable right? Using the AIO has some appeal because it sets everything up.

So I had some more discussion about all this on the Nextcloud help forums. That discussion can be found here. It appears there is no support and there never will be for using something other than docker volumes (no mounting of folders). Does anyone know what disk these docker volumes end up on in Unraid? Is it in the OS on the RAM? Does it go on the USB or maybe in the docker.img? Is moving the Docker volume location something that would persist over reboots? I do think it may be worth facilitating a way this container to work on Unraid because it would give a low maintenance way for less tech savvy people to get a whole Nextcloud setup easily.

So I upgraded my hardward and did see improvement particularly when I first access nextcloud. Things are still a bit slower that I would like but not too bad. I figured now would be the time to upgrade to the offical docker container. I am having some trouble getting the "Nextcloud all-in-one" container, that seems to be the offical way to install it, to work. Is that the right container to use? As I have been updating containers I have been trying to use docker-compose so it is easier to backup the configuration for the future. Below is the compose I am attempting to use. I would like nextcloud to be on vlan that is isolated from the rest of my network. That is what br0.70 is. This networks methon is working for other containers I have. I have also left off the ports, like I have done with my other containers that work, because this should have it's own IP address. I think I have setup properly to store my Nextcloud data on a particular share on my unraid but wouldn't mind confirmation. When I run this it says "service "nextcloud-aio-mastercontainer" refers to undefined volume nextcloud_aio_mastercontainer: invalid compose project". This seems to refer to a line I'm not supposed to change according to the documentation. services: nextcloud-aio-mastercontainer: image: nextcloud/all-in-one:latest container_name: nextcloud-aio-mastercontainer restart: unless-stopped networks: br0.70: ipv4_address: 10.24.70.40 environment: NEXTCLOUD_DATADIR: "/mnt/user/nextcloud" volumes: - nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed - /var/run/docker.sock:/var/run/docker.sock:ro networks: br0.70: external: true I realize I may have to take some of these questions to the Nextcloud forums but thought I would start here. Thanks in advance for the help.

@IntertekLTC Thank you for the response. Right now I am leaning towards picking up a couple 2.5" ssds and a sata controller. In the future when I upgrade the system as a whole I will go to NVME. I think that will be a big performance bump at a reasonable price for right now. When I do that I will switch to the official Nextcloud image and start a clean install.

I've been using linuxserver's version. I have always had good luck with their containers. It doesn't seem too slow after the first time I access each day. I could be wrong but it feels a lot like the disks spinning up on first access. I get similar delays playing a movie from plex. Would the official implementation improve that?

I am looking into making some upgrades to my unraid box. The biggest reason is I am using Nextcloud more and it is slow to load. I think this is the case because I have my Nextcloud data on the array for protection but that means the drives have to spin up to do anything with it. With that thought, I have my first question. Is there a performance boost moving the Nextcloud data off the array into a cache pool? That leads to the next consideration. I want some protection for my Nextcloud data. Right now that is accomplished with the data being on the array and the parity that gives. I'm not an expert but it seems like I could get similar protection and better performance with my cache being on a RAID of SSDs. I would set up a pool using to SSDs in a BTRFS Raid. I would like to use 2x2TB SSDs to have plenty of space. Do I understand that correctly? Can you have multiple pools? Would it be worth moving all the old app data over to the new pool? Assuming the above is true the ideal solution would be to put a couple of 2TB NVME drives into the computer and make them the cache pool. My motherboard is old enough to not have NVME drive connectors. That means I would need a new MB and CPU (and probably RAM). Since I am upgrading all that I would like it seems like it would be time to do the case (from Lian-Li PC-Q25 to Define XL7 maybe) too. There are a couple of reasons for that. I would like more space in the case for drives. I would like more PCI-E to be able to add a GPU down the line (for VMs or encoding). The thing is I don't really need extra performance or storage right now. That seems like a giant set of upgrades just to get some better cache storage. Is there a way to add 2 NVME drives to an older MB maybe via PCI-E? Would I need PCI-E bifurcation to do that for 2 drives? Is there a benefit to adding SATA ports via PCI-E and connecting the SSDs to that? Or does SATA limit the performance benefit to keep it small? More than anything I am looking to improve the Nextcloud performance without spending too much money or making a brand new NAS right now. I might be ready to upgrade the whole thing next year sometime but it could be a few years before the full upgrade. Thanks for the help and advice.

I am thinking about rebuilding some of the docker infrastructure I have built up over the last 8 years. In looking at what I want to change I have come across a bit of a dilemma. Should I keep using the built-in docker management or change to something like docker-compose or portainer. I have what I see as a few pros and cons. Unraid Built-In (pro) the availability of the community apps plugin (pro) the ability to easily get to the webui, console, or logs of a container (pro) docker-folders makes organizing easy (pro) ease of updates (cons) have to remember which containers start first docker-compose (pro) the ability to quickly rebuild the setup with just a file (pro) the ability to use dependencies to adjust the autostart order (pro) appears like it shows up with the other dockers (cons) harder to access the webui, console, or logs of a container portainer (pro) all the abilities of docker-compose with a nice ui I don't think I want to add another UI so portainer is out unless it offers something more. All this leaves me more or less even between docker-compose and the unraid built-in. I really like the ability of the dependencies and the recovery if something happens to my server that docker-compose provides. However I use the webui button all the time and the logs in invaluable for troubleshooting. Does any one here have any hands on experience to add that might sway this one way of the other? Is there a feature or complication not listed here worth knowing?

After reboot you lose the edit and web ui options for a container along with its Image and version info. Is this something that happens for everyone or is it just me?