kahst
Fixed Dockerfile and added documentation for the Docker usage
I have fixed the Dockerfile. Apparently it fixes #602 . Also added documentation for usage of BirdNET-Analyzer in Docker. For now, Dockerfile will install the module and will switch to /input directory. User has to mount 2 directories: 1) His directory with input files to /input, 2) A directory where analyzer will output results to /output. Documentation describes it and gives an example.
Regarding the build I added TARGET argument, that is referenced as a target for additional dependency setup. By default it is set to all. User can define it via --build-arg argument while building the image.
Ok, I didn't notice there is already a Docker workflow established (as in tests of Docker Build), but it wasn't described. I can modify the Dockerfile (last workdir to /audio) and modify documentation, or you can modify test files of Docker build. Which approach should we follow?
I have update Dockerfile and Github Docker workflow. As previously, you can select which module you would like to run (entrypoint of the Docker container will by python3). I changed /audio to /input (as not all birdnet modules request only audio files), also added /output for the output files. In some occasions it is more beneficial to have /output as a separate mount, since your input data maybe mounted to some network locations (or cloud data) and your /output will be mounted to your PC.
Thinks have changed alot, we might come back to this later, but closing for now
