fix for copy command - from remote to local #3749
Merged
+2
−1
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 is the feature/update/fix?
Fix: Resolved
convox cp
Issue for Remote to Local File CopyThis update addresses an issue with the
convox cp
command when copying specific files from a remote container to the local filesystem. Previously, attempts to copy individual files (as opposed to entire folders) appeared to succeed, with network traffic passing, but the file would not be created on the local system. This fix ensures that single files can now be reliably copied to the local filesystem.How to use it?
The
convox cp
command is used to copy files between a local machine and a container. To copy a file from a container to your local system, you’ll first need the container ID, which can be obtained with:Then, to copy a specific file from the remote container to a local directory, use:
For example:
Requirements
To use this feature, you must be on at least CLI and rack version
20241112202208
.convox version
.convox update
.convox rack -r rackName
.convox rack update -r rackName
.