tar -xf --no-same-owner
Option Not Supported on OpenWrt Remote Host for Extracting VS Code Server
#10603
Open
6 tasks done
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServer
setting[Optional] Diagnose with Copilot
I asked @remote-ssh and it helped, but I still want to report this bug
In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?
I COULD successfully SSH to the remote machine with the generated SSH command
Remote-SSH Log
Remote-SSH Log
Expected Behavior
tar successfully unzip the code-cli-$COMMIT_ID.tar.gz
I tried the snippet below, and it allows me to successfully establish connection.
root@ImmortalWrt:~/.vscode-server# tar -xf vscode-cli-fabdb6a30b49f79a7aba0f2ad9df9b399473380f.tar.gz --no-same-owner tar: unrecognized option: no-same-owner BusyBox v1.36.1 (2023-11-19 17:02:49 UTC) multi-call binary. Usage: tar c|x|t [-zahvokO] [-f TARFILE] [-C DIR] [-T FILE] [-X FILE] [FILE]... Create, extract, or list files from a tar file c Create x Extract t List -f FILE Name of TARFILE ('-' for stdin/out) -C DIR Change to DIR before operation -v Verbose -O Extract to stdout -o Don't restore user:group -k Don't replace existing files -z (De)compress using gzip -a (De)compress based on extension -h Follow symlinks -T FILE File with names to include -X FILE File with glob patterns to exclude root@ImmortalWrt:~/.vscode-server# tar -xf vscode-cli-fabdb6a30b49f79a7aba0f2ad9df9b399473380f.tar.gz -o tar: invalid tar magic root@ImmortalWrt:~/.vscode-server# tar -xzf vscode-cli-fabdb6a30b49f79a7aba0f2ad9df9b399473380f.tar.gz -o root@ImmortalWrt:~/.vscode-server# l -rwxrwxr-x 1 root root 22070072 Dec 19 18:29 code* -rw-r--r-- 1 root root 9046413 Jan 2 10:11 vscode-cli-fabdb6a30b49f79a7aba0f2ad9df9b399473380f.tar.gz
Actual Behavior
In the script
tar -xf vscode-cli-$COMMIT_ID.tar.gz --no-same-owner
is used to unzip the gz, which do not work in remote host like openwrt.Steps To Reproduce
Create a machine with OS Immortalwrt and try to connect to that host.
Anything else?
No response
The text was updated successfully, but these errors were encountered: