Beiträge von fliwatuet

Open a console, go to the /srv folder and then cd to the folder where your shared folder is located and do a

ls -al

to find out the owner of the files and folders. User and group 0 means "root", which is not a good idea.

I also found out, that it might be better to use the chown command rather than the OMV stuff. It also might help if you remove the old docker volumes when you started over and over again.

Thank you @gderf to use the fully qualified system path names solved the issue completely. I found the paths in the srv-folder.

I followed the videos from technodadlife, he always uses the shared folders which seems to be not recommended.

Zitat von gderf

I use the fully qualified system path names instead.

How do I do that and how do I handle the permissions?

Here we go:

and

The user 1002 has read, write and execute permissions.

Hi everybody!

I am trying to set up a container using the above mentioned docker image.

My config is working well, everything seems to be okay. Until I restart the server.

After the reboot the container is running but I have no access to the backend.

The log says

Error:Can't write to logfile

I then have to stop the container, delete it and start all over again. Then everything works fine, even the sabnzbd config is intact.

In OMV I set Owner and Group to the same user/group I used for the container (PUID and PGID) but it will never survive a reboot.

Is there anything I can do?

Best regards
fliwatuet