Addressing persistent volume permissions issue and default user creation inside the image #409
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the docker image has a default user "app" with the uid and gid set to 1000. this is causing difficulty in mapping the persistent storage from the host with a different uid and gid. Addressed in this issue #403. Not sure what exactly is the purpose of the default user inside the image.
I removed the default user creation and now the user & group gets created as part of the entrypoint script based on the uid and gid given from the docker run command as an env variable. The changes in this PR will take care of the user permissions of the directories mounted.
I am using this updated docker images in my homelab and I have no problem in using the blackcandy to play songs till now. Hope this is helpful