Fix export artifact volume permissions - #692
Open
ryan-mahoney wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
nobodyruntime user so fresh Docker volumes inherit writable ownershipVerification
mix test test/gtfs_planner/gtfs/task_artifact_config_test.exs— 5 tests, 0 failuresmix precommit— 3,471 tests, 0 failures, 5 skippedDeployment note
Existing Docker volumes retain their current ownership when a new image is deployed. Any existing root-owned task-artifact volume requires a one-time ownership correction; fresh volumes inherit the image ownership.