Closed rfrowe closed 3 years ago
I am a bot, here are the test results for this PR: https://ci-tests.linuxserver.io/lspipepr/nzbget/v21.0-pkg-a7f1c907-pr-121/index.html https://ci-tests.linuxserver.io/lspipepr/nzbget/v21.0-pkg-a7f1c907-pr-121/shellcheck-result.xml
Thanks for the PR, but this could have a significant impact slowing down container init times for many users. I would advise if you require this functionality to do the permissions manually as needed or check out https://blog.linuxserver.io/2019/09/14/customizing-our-containers/
@nemchik May I ask how you would feel about a PR which does [[ -d /intermediate ]] && chown abc:abc /intermediate
? A similar chown
is done for /config
and /downloads
which may also be mounted volumes. It seems only fair that /intermediate
be chowned as well since it's officially supported in the README. This would solve issue (2) of my original post, which is a good enough solution for me.
Description:
So I was trying to mount an SSD-backed volume for the intermediate directory. I read the note about this in the README but happened upon two facts:
/intermediate
I could have submitted a PR to add conditional chown of
/intermediate
to cont-init.d, but I decided to fix both problems. By recursively chowning/downloads
, I can mount my volume to/downloads/intermediate
since docker supports nested volume mounts. This then fixes both issues.Benefits of this PR and context:
Plug-and-play functionality for intermediates volume.
How Has This Been Tested?
Did
docker-compose down -v
and altered mydocker-compose.yaml
to replaceimage:
with:Then did
docker-compose up
. No longer receive permissions error about/downloads/intermediate
while downloading.Source / References:
N/A