Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using remote containers on ARMv64 (Jetson Nano) fails (wrongly installs vscode-server-linux-64) #1716

Closed
hlacikd opened this issue Oct 23, 2019 · 8 comments
Assignees
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality verification-needed Verification of issue is requested verified Verification succeeded
Milestone

Comments

@hlacikd
Copy link

hlacikd commented Oct 23, 2019

  • VSCode Version: 1.40.0-insider
  • OS Version: Linux pop-os 5.3.0-19-generic (local host), Linux jetson 4.9.140-tegra (remote host, running containers)

Steps to Reproduce:

  1. Create local devcontainer.json
    {
    "image": "ubuntu",
    "workspaceFolder": "/pcrdev",
    "workspaceMount": "src=pcrdev,dst=/pcrdev,type=volume,volume-driver=local"
    }

  2. Launch Remote-Containers Open Folder in Containers

  3. Wait during Installing Dev Container, Copying VSCode Server to container

Wrong extension architecture is installed (x64 instead of ARMv64)

  1. Error Occures - Visual Studio Code - Insiders An Error ocurred setting up the container.

Screenshot from 2019-10-23 17-13-16

However when using Just Remote SSH Development, correct version of vscode-server is installed (ARMv64) so this bug is valid only for remote containers on ARMv64

@chrmarti chrmarti transferred this issue from microsoft/vscode Oct 24, 2019
@chrmarti chrmarti added containers Issue in vscode-remote containers feature-request Request for new features or functionality labels Oct 24, 2019
@chrmarti chrmarti added this to the Backlog milestone Oct 28, 2019
@hlacikd
Copy link
Author

hlacikd commented Oct 30, 2019

Excuse me but why is this a feature request and not a bug? For sure it is possible to do remote development (SSH) with VSCODE INSIDERS on arm64 architecture, therefore same version vscode remote development could be deployed inside container. Because of that, its just a matter of install script (choosing correct install package (arm64 over x64) during development container deployment.

@chrmarti
Copy link
Contributor

Adding support for ARM64 in Insiders and ARM32 in general.

@chrmarti
Copy link
Contributor

Verification using emulators:

docker run --rm --privileged hypriot/qemu-register
docker run -d arm32v7/ubuntu sleep infinity
docker run -d arm64v8/ubuntu sleep infinity

Then attach to the two containers with Remote-Containers.

@chrmarti
Copy link
Contributor

ARM64 will be enabled in the next VS Code stable release too.

@hlacikd
Copy link
Author

hlacikd commented Dec 3, 2019

using docker run -it --rm --gpus all arm64v8/ubuntu

then attaching vscode insider 1.41.0 to this container results in error :
[1138 ms] /root/.vscode-server-insiders/bin/7cf4cca47aa025a590fc939af54932042302be63/server.sh: 12: /root/.vscode-server-insiders/bin/7cf4cca47aa025a590fc939af54932042302be63/server.sh: /root/.vscode-server-insiders/bin/7cf4cca47aa025a590fc939af54932042302be63/node: Exec format error
[1212 ms] Command failed: docker exec -w /root/.vscode-server-insiders/bin/7cf4cca47aa025a590fc939af54932042302be63 -u root -e SHELL=/bin/bash -e VSCODE_AGENT_FOLDER=/root/.vscode-server-insiders bbd4deeea942f7e33682cb80b1a6e31b503c4f69b6c6e4726c39b7453a5a3fcb /root/.vscode-server-insiders/bin/7cf4cca47aa025a590fc939af54932042302be63/server.sh --disable-user-env-probe --port 0

@chrmarti
Copy link
Contributor

chrmarti commented Dec 3, 2019

@hlacik Please check you are running the latest version of the extension (currently 0.86.0).

Maybe you attached to the same container with an earlier version of the extension. If so, try deleting the /root/.vscode-server-insiders folder in the container (or use a new container) and attach again.

@chrmarti chrmarti added the verification-needed Verification of issue is requested label Dec 3, 2019
@hlacikd
Copy link
Author

hlacikd commented Dec 3, 2019

@hlacik Please check you are running the latest version of the extension (currently 0.86.0).

Maybe you attached to the same container with an earlier version of the extension. If so, try deleting the /root/.vscode-server-insiders folder in the container (or use a new container) and attach again.

Oh, so after TODAY insider update 1.41.0-1575351432 it finally works , your awesome guys, right on time, I have one week before project delivery (running on nvidia jetson nano) and I can finally remote debug inside containers running there.

@alexr00
Copy link
Member

alexr00 commented Dec 4, 2019

Looks like this is verified by the original issue filer!

@alexr00 alexr00 added the verified Verification succeeded label Dec 4, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality verification-needed Verification of issue is requested verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants