add --no-same-owner option to tar #3456
Open
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
|
Thanks for opening your first pull request for MusicBrainz Server, and welcome to our community! 🎉 |
|
Can one of the admins verify this patch? |
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.
Problem
I'm running a setup to deploy the server docker using helm and using the previous Ubuntu version. I currently get the error when running the createdb.sh
mbdump/artist_alias_type tar: mbdump/artist_alias_type: Cannot change ownership to uid 1000, gid 1000: Operation not permitted.More on the issue here
Solution
Added the
--no-same-owneroption to the tar commandTesting
I tested this by running the the createdb.sh again and the import tar command was successful.