Add nextcloud.initLock to set NEXTCLOUD_INIT_LOCK #343
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.
Pull Request
Description of the change
This allows setting
NEXTCLOUD_INIT_LOCK
, see nextcloud/docker#1760Benefits
If running multiple replicas, this will avoid them walking over each other when upgrading.
Possible drawbacks
If an upgrade is aborted in progress, the lock file might be left behind. You will have to manually delete it before another upgrade can be attempted. This is an issue in the Docker image that I filed here: nextcloud/docker#1903
Applicable issues
Checklist
Chart.yaml
according to semver.