vscode-remote-release icon indicating copy to clipboard operation
vscode-remote-release copied to clipboard

VSCode Remote Development does not work with Photon OS Container

Open RamWebDev opened this issue 3 years ago • 0 comments

When trying to use Remote Container to attach to Photon OS container (https://hub.docker.com/_/photon), it fails with the below error in the VSCode terminal

================================= 22 ms] Remote-Containers 0.241.3 in VS Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a). [21 ms] Start: Resolving Remote [23 ms] Setting up container: /type-express-srv4 [30 ms] Start: Run: docker inspect --type container /type-express-srv4 [149 ms] Start: Check Docker is running [149 ms] Start: Run: docker version --format {{.Server.APIVersion}} [292 ms] Server API version: 1.41 [293 ms] Start: Inspecting container [293 ms] Start: Run: docker inspect --type container 6461f8496631948afcf481adcec4569c678cd0847a2cf202230f4e7cb2c40d79 [367 ms] Start: Run in container: /bin/sh [369 ms] Start: Run in container: uname -m [569 ms] aarch64 [569 ms] [569 ms] Start: Run in container: (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null [574 ms] NAME="VMware Photon OS" VERSION="4.0" ID=photon VERSION_ID=4.0 PRETTY_NAME="VMware Photon OS/Linux" ANSI_COLOR="1;34" HOME_URL="https://vmware.github.io/photon/" BUG_REPORT_URL="https://github.com/vmware/photon/issues" [574 ms] [574 ms] Start: Run in container: cat /etc/passwd [579 ms] Start: Run in container: test -d /root/.vscode-server [582 ms] [583 ms] [583 ms] Start: Run in container: test ! -f '/root/.vscode-server/data/Machine/.writeMachineSettingsMarker' && set -o noclobber && mkdir -p '/root/.vscode-server/data/Machine' && { > '/root/.vscode-server/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null [586 ms] [586 ms] [586 ms] Exit code 1 [586 ms] Start: Run in container: cat /root/.vscode-server/data/Machine/settings.json [590 ms] [590 ms] cat: /root/.vscode-server/data/Machine/settings.json: No such file or directory [590 ms] Exit code 1 [590 ms] Support for ARM64 is in preview.

[590 ms] Start: Run in container: test -d /root/.vscode-server/bin/3b889b090b5ad5793f524b5d1d39fda662b96a2a [593 ms] [593 ms] [593 ms] Exit code 1 [593 ms] Installing VS Code Server for commit 3b889b090b5ad5793f524b5d1d39fda662b96a2a [594 ms] Start: Installing VS Code Server [594 ms] Start: Run in container: mkdir -p /root/.vscode-server/bin/3b889b090b5ad5793f524b5d1d39fda662b96a2a_1659239364084 [599 ms] [599 ms] [625 ms] Start: Run in container: (dd iflag=fullblock bs=8192 count=6258 2>/dev/null; dd iflag=fullblock bs=2631 count=1 2>/dev/null) | tar --no-same-owner -xz -C /root/.vscode-server/bin/3b889b090b5ad5793f524b5d1d39fda662b96a2a_1659239364084 [636 ms] [636 ms] zcat: not gzip [637 ms] Start: Run in container: mv -n /root/.vscode-server/bin/3b889b090b5ad5793f524b5d1d39fda662b96a2a_1659239364084/* /root/.vscode-server/bin/3b889b090b5ad5793f524b5d1d39fda662b96a2a && rmdir /root/.vscode-server/bin/3b889b090b5ad5793f524b5d1d39fda662b96a2a_1659239364084 [662 ms] Shell server terminated (code: 2, signal: null)

===========================

This is easily reproducible with a simple NodeJs application

RamWebDev avatar Jul 31 '22 04:07 RamWebDev