Fix EACCES errors with package*.json #6225
Merged
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
Apparently: > All new files and directories are created with a UID and GID of 0, unless the optional --chown flag specifies a given username, groupname, or UID/GID combination to request specific ownership of the copied content. https://docs.docker.com/engine/reference/builder/#copy Why this never broke stuff before? No clue. Could be because we updated to node 16. Could be because of a docker update.
cdrini
changed the title
cdrini
changed the title
|
Actually gitpod now errored with a different error :(
|
cdrini
added
the
On testing.openlibrary.org
|
thank you!! |
jimchamp
removed
the
On testing.openlibrary.org
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.
Closes #6224
Fix. Apparently:
https://docs.docker.com/engine/reference/builder/#copy
Why this never broke stuff before? No clue. Could be because we updated to node 16. Could be because of a docker update.
Technical
Testing
Screenshot
Stakeholders