Openmediavault and organizer - a difficult history

[wintuxx]

I have Openmediavault running on my Raspberry PI 4. As has been discovered in the meantime, this NAS system is very sensitive and does not tolerate any other services on the host system.

In any case, I did not notice this difficult relationship directly. I was only ever surprised that after a while the mergerFS service disappeared.

During the last reinstallation of OMV, I immediately noticed that after the installation of pip-3 and organiser, no changes could be made to the shares. So I identified the solution to the problem.

However, I did not want to do without the comfort of organzier. Since I had already had some contact with Docker, I came up with the idea of running organzier in a Docker container.

Since I have no experience in creating images and containers, I looked for a suitable template. I found one at https://github.com/dskaggs/docker-organize. The solution in this respotory did not meet my requirements, but I was able to work with the Dockerfile and the script.

With the given data on how to start a container, I was able to create a working docker-compose, which creates a container as I need it.

During my first attempts, I noticed that the files that were edited by organizer in the docker container were taken over by root.

I solved this by creating the user pi in the docker file and having it execute organizer.

I use Organizer mainly for automated sorting of files.

This is done very successfully with the Docker container.

I have created a fork of the Respotory where I document my changes.

https://github.com/wintuxx/docker-organize

Translated with www.DeepL.com/Translator (free version)