fix: removed changing ownership at the beginning of container start

[kylhuk]

Description

A chown of a download directory might lead to unwanted effects, as there are users who already have a working environment and want to switch to NZBGet. The chown is unnecessary, as the check if the necessary folders are existing and/or are writable happens somewhere else.

Here the issue to this PR: #217

Testing

Built the container in my environment and was able to run it successfully.

[luckedea]

We can't remove chown completely here since it would break fresh docker installs.

[kylhuk]

We can't remove chown completely here since it would break fresh docker installs.

I disagree. The app could still run. In the WebUI you will then see error messages about some path issues. Additionally, I checked other, similar apps like sabnzbd, radarr and sonarr. No one is doing a chown while starting the docker container. So I think it would be good practice to move the permission problems to somewhere else, as currently you only support fresh installs, instead of supporting fresh and existing installs.

[luckedea]

@kylhuk

I see your point.

We want to support all types of installs.

Other similar apps do have some sort of ownership/permissions checks too, it's not always a direct chown, and we have to do it - otherwise nzbget won't be able to work correctly with that folder.

Can you update your PR to only remove the -R please? I believe that should be the best compromise here.

[kylhuk]

@luckedea agreed, removed the -R for both chown, for /config and /downloads

[phnzb]

@kylhuk
Thank you for contribution! Merged to develop.