nextcloud-snap VS docker

First of all I don't really know much about snaps, but after reading https://github.com/nextcloud-snap/nextcloud-snap for a bit I understood that the nextcloud installation is stored in /var/snap/nextcloud/current/ and the files are stored in /var/snap/nextcloud/common/ While you could just backup the folders, this would not solve moving, and for that I think that the easiest way would be moving from a snap installation to a php installation. I found this guide, but the main thing is that it's old, complicated and I don't think it is the best way: https://github.com/nextcloud-snap/nextcloud-snap/wiki/Migrating-from-nextcloud-snap-to-Nextcloud-server I'd do it like this: 1. Change the nextcloud snap ports into something else than 80 and 443 2. Install the mysql, apache, php and the needed php and apache modules normally. 3. Install nextcloud in this configuration 4. Copy the data and apps from snap into the webserver directory that I installed nextcloud to 5. Copy the database 6. Get a ssl certificate with certbot

As pointed out by people at nextcloud, snaps are not confined on ditros other than Ubuntu.

I don't know which one is the "best" however there are concerns over how "universal" snap's sandbox strength is, like here.

I found this github page, where they describe a problem similar to yours https://github.com/nextcloud-snap/nextcloud-snap/issues/1618

Hello. I am following this guide: Change data directory to use another disk partition · nextcloud-snap/nextcloud-snap Wiki · GitHub to attach NFS share which is mounted to my Ubuntu VM to NC which was installed via snap After completing all the steps from section “If you have already created an admin user” I am getting the following error message:

To be honest, this sound like an aweful strategy. I think you would be better off using a regular ubuntu VM and install nextcloud-snap. It is auto-updating and self-contained, so that you do not have to manage any dependencies yourself. It also includes a built-in backup machanism, so you could also reinstall the whole VM if upgrading goes wrong and simply restore your nextcloud from scratch.

But also if you just want to run Nextcloud, the snap package is a lot better to be honest, stays up to date better and can be accessed directly instead of having to log into umbrel and then nextcloud. I started the same way as you but ended up going the direct route instead. My Ubuntu machine is called “server” so I can just log in via http://server.local. https://github.com/nextcloud-snap/nextcloud-snap

Am I better off using this container: https://hub.docker.com/_/nextcloud/

It looks like I'm not the only person who has faced this. apache-based images require buster, for instance, and some docker images that rely on Ruby face issues too (for example, I decided to try setting up Postal but it looks like it's facing the same issues).

If you look at the info on https://hub.docker.com/_/nextcloud, you'll see that you aught to be specifying at least one volume, so that you have the data you want to not disappear on restart, and can access config files.

Yes, and this is what L passed through as the env variables in the docker compose file, as the docs state: https://hub.docker.com/_/nextcloud

You can't map binaries from host to container like this. What you need is a custom Dockerfile that installs ffmpeg. https://github.com/nextcloud/docker/blob/master/.examples/dockerfiles/full/fpm/Dockerfile

A good example to start with is at https://github.com/nextcloud/docker/tree/master/.examples/docker-compose/insecure/postgres/apache

Nextcloud is free and open source. The easiest way to install it is via docker containers. nextcloud docker