Restores the tar command to its original state#21
Merged
Conversation
4477bdb to
9d8041c
Compare
ab5a017 to
efe662b
Compare
9e45375 to
3112d09
Compare
53ea73b to
3d65e73
Compare
c3234f7 to
d2b7cc5
Compare
d2b7cc5 to
5feb572
Compare
Contributor
Author
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
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.
What
This PR tries to reduce side effects by:
tarcommand to its original stateWhy
We are using
chmod u+s "$(command -v tar)"to setuid on tar (This is needed because we are caching/nix/and other directories outside of~, which is owned byroot)This has a problem where it changes the parent directory of
~/.cache/nixto be owned byrootinstead ofrunner.I thought #22 had fixed it, but we ran into similar issues when we use a go cache on top of the devbox cache.
Caveat
Cache enabled on self hosted Linux may stop working