alpine-mariadb VS docker

I currently use the linuxserver nextcloud image with the mariadb image from yobasystems because it's more lightweight than others I've found. Happy to share my docker-compose.yml file if useful. I have been intending to migrate to the official nextcloud image but haven't found a good time to do it yet. I trust linuxserver images enough, they have a good reputation, but I like to be as close to upstream as possible. Mariadb is one example where the arm architecture isn't officially supported. I chose a third-party image rather than built my own because nextcloud was one of the first things I migrated over to docker before I learnt how to build images. Goes to show learning docker does take time :)

Try https://github.com/yobasystems/alpine-mariadb

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