Improve performance of in-container commands with many write on disks #3
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 improves container disk performance for the
npx create-react-app
command and fixes #2 by using in-container storage instead of mounted storage.As excerpted from the updated README.md as follows, this PR includes a bash script to preserve files from remote container to user's host directory.
NOTE: You will find the
boyaki
directory in your remote container during the workshop (so as in the VSCode's explorer) but NOT in your host machine. This is a side-effect of the fix PR #3 (for the issue #2) to speed up thenpx create-react-app
command, thus you may lose yourboyaki
files once you stop the remote container. If you need to preserve and/or edit the files inside theboyaki
folder outside of your remote container, you can use the bash scriptcopy-boyaki-to-host.sh
to copy those in-container files as a zip fileboyaki.zip
to your host machine'sboyaki
directory. Simply execute/workspaces/hostdir/copy-boyaki-to-host.sh
/hostdir/copy-boyaki-to-host.sh
inside your remote container and follow the guidance to run it.