stego-toolkit VS docker

Other then that: - use `exiftool` not `exiv2` (it was able to read way more metadata last time I tried) - would definitely try `LSBSteg` and `foremost`, see more here at https://github.com/DominicBreuker/stego-toolkit - https://stegonline.georgeom.net, check out the different color masks to see if there isn't some information hidden in the color bits. Often, but not always, seeing varying pixels in one or two color channels means some kind of stego was applied or otherwise it's some custom encoding => imagemagick + python to extract)

This stego-toolkit links to a program called AudioStego in C++ that you can install with cmake.

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