Fix failing Skopeo pullImage with /run/containers not readable
#122
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
norpol
commented
Mar 10, 2024
norpol
changed the title
/run/containers not readable
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.
I've just debugged for someone why Skopeo fails with
reading JSON file "/run/containers/1001/auth.json": open /run/containers/1001/auth.json: permission deniedinside GitHub actions.I think that is something also true for
nix2container.pullImage, though I'm not sure how/where you would like me to add this change. Needs probably some further investigation.To test this run
mkdir /run/containers; chmod 000 /run/containersand see Skopeo pull failing.NixOS/nixpkgs#294849