build: Set owner on /usr/local/cargo/registry/ in Dev Container #5018
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
This was referenced Nov 22, 2024
richb-hanover
changed the title
eitsupi
changed the title
Co-authored-by: eitsupi <[email protected]>
eitsupi
approved these changes
Jan 12, 2025
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.
This PR seems to address #5007 and #4974 which were related to reports of "not being able to build the Playground from a fresh installation of the Dev Container."
The answer seems to be to add
sudo chown vscode /usr/local/cargo/registry/to the postCreateCommand section of the Dev Container's JSON file.There were SO MANY red herrings here...
Some operations gave an error trying to create a file in
/usr/local/cargo/registry...(this was the hint toward the solution)The initial report gave a mysterious ENOENT error out of the blue. That seemed to be caused by the failure to have installed wasm_pack. Using
npm install wasm-packcaused that to go away.cargo cleandoes indeed remove all the cached cargo files, but gives the "resource busy" on /workspaces/prql/target (which remains today)I am content. I'm back to a steady state - I can build the Playground, Book, and Website from a dev container.