-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: chown shenanigans #410
Conversation
also fixing the startup order, should go: |
I am a bot, here are the test results for this PR:
|
I am a bot, here are the test results for this PR:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
@martabal you think running chown in the background is the best way? |
I am a bot, here are the test results for this PR:
|
IMO, it is not. Someone who misconfigured his share won't realize this issue and this solution will impact people who don't have permission issues. |
How about this* |
I think we'll have the same issue #273. We probably want to check if |
this is not a recursive chown, its just the photos folder, and subdirectories 1 depth |
I am a bot, here are the test results for this PR:
|
Will this work for files not owned by the |
Co-authored-by: martin <74269598+martabal@users.noreply.github.com>
I am a bot, here are the test results for this PR:
|
I am a bot, here are the test results for this PR:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It still does not work ./run: line 7: 8: command not found
my bad |
any other changes or good to merge? |
I am a bot, here are the test results for this PR:
|
Another issue caused during the first install: |
find /app/immich -path "*/node_modules" -prune -o -exec chown abc:abc {} + | ||
lsiown -R abc:abc \ | ||
/config | ||
[[ "${APPLY_PERMISSIONS}" == "true" ]] && lsiown -R abc:abc "${IMMICH_MEDIA_LOCATION}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with it but maybe we should have it for /config
too ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/config should always be mounted locally, and not our problem if mounted any other way IMO
spawns chown in the background as a 'lazy' way of hopfully negating init stalls
also format scripts and update arm dockerfile