NextCloudPi VS docker

nextcloudpi.com

It works great and is reasonably fast if you connect it over ethernet. If you have a newer firmware, which has already enabled the boot from SSD on your pi it is super easy (otherwise just Google how to set up boot from ssd with a microSD). Afterwards you can use the raspberry pi flashing tool to flash the image of nextcloudpi on your ssd. This includes the 64bit raspberry pi OS, a running Nextcloud instance and some other handy tools (like help to set up security features). The first setup can be done with the IP adress of your Pi in an internet browser of a device in your network. Here is the link to the image of NextcloudPi https://github.com/nextcloud/nextcloudpi

Issue 2 still persists and after digging around found this issue reported on git https://github.com/nextcloud/nextcloudpi/issues/1752 but cant figure out how to sort it

Install nextcloudpi (https://github.com/nextcloud/nextcloudpi) Install Nextcloud app on your phone.

If you want to update faster than the docker image is published, you'll have to build the image locally: https://github.com/nextcloud/nextcloudpi

My best experience in out of the box comes from Nextcloudpi: https://nextcloudpi.com/

Nextcloud is functionally similar to Dropbox, Office 365 or Google Drive but is self-hosted so you are in control of your data. This version is a lightly-forked version of NextCloudPi, which was developed for SBCs like the Raspberry Pi. Only a few changes from upstream and some SysV initscripts were required to get this working nicely in Linux Deploy.

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