fix: initContainer execution with skipChown enabled #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ontainer) - adjusted ci to disable skipChown (like it was before due to the wrong check)
xoxys
approved these changes
Jun 19, 2023
|
|
Will create another PR for that. |
For the record: no new PR for that as the volumes were also not handled by chmod in the container: https://github.com/owncloud-docker/base/blob/62d4e7ff12f79fd3a02b17ab6fdca432605ca870/latest/overlay/etc/owncloud.d/25-chown.sh#L37 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 initContainer for Chown is executed even if it should be skipped as the wrong value is referenced. This PR fixes this issue.