docs VS docker

I will recommend you review the documentation for the official Postgresql docker images which you can read here.

This is the full documentation for these images. Please note, this page has links to Docker official documents on volumes, etc., which are necessary to run images such as this.

We've just followed the official documentation to add a PostgreSQL database server. This will act as an application container, as our app will soon be depended on it. And in order to make sure that the database container is always started whenever we start our application container, we've added a new depends_on key to the app service and let it know which other service(s) it, well, depends on. This will make sure that the database server is up and running before the app. You may also have noticed that we've mounted volume to our database server's datapath a bit differently. This is known as "named volume". We'll discuss it a bit more in another part, it's not relevant to what we're learning here.

Nextcloud isn't hard to setup, follow the official doc https://github.com/docker-library/docs/blob/master/nextcloud/README.md

Looking at the setup for this (link here: https://github.com/docker-library/docs/blob/master/nextcloud/README.md), I am starting to understand a lot of the recent posts that we've seen & how much of a mess it still is :(

Coming back to nextcloud, the official readme of the nextcloud image has a few notes on how to set up both nextcloud versions.

Use the native command envstubst to replace the Auth Tokens in your Config File before starting NGINX. Example: https://github.com/docker-library/docs/tree/master/nginx#using-environment-variables-in-nginx-configuration-new-in-119

It's not clear why you want to split the web server (nginx) and the app (nextcloud). However, if you do have a good reason, you're in luck, they have a compose file that does just that: https://github.com/docker-library/docs/blob/master/nextcloud/README.md#base-version---fpm (version 2, but it'll work)

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