Skip to content

VSCODE

VSCODE can be connected to a running container for development purposes by using SSH connection.

The interactive SSH endpoint offers a stable connection to be connected to VSCODE. This provides you with a secure SSH connection to the container.

How to run SSH workloads?

Latest ubuntu dev docker images are recommended.

Obtain workload SSH credentials

To view the SSH connection options, navigate to the workload in the dashboard. Once the workload is in the Running state, on the right-hand side of the workload details page, scroll down to the Interactive Endpoints section.

Click on the Connect button to reveal the SSH URL and Password for your container as shown below. 

ssh -o strictHostKeyChecking=no -p <port> <username>@<hostname>

For example:

ssh -o strictHostKeyChecking=no -p 8001 aac@aac5.amd.com

The Password field will contain a password used to authenticate the SSH connection.

VSCODE configuration

Install dependencies

Plugin to connect to remote ssh servers vscode-remote-extension.

Configure the SSH connection

Copy the SSH URL from Plexus and use it to configure your ssh connection.

  • Add it directly into the .ssh/config file of your home path.
Host workload-aac5
  HostName aac.amd.com
  strictHostKeyChecking no
  ServerAliveInterval 60
  Port 8001
  User aac
  • Include ssh command into the VSCODE configuration, as shown in image:
  • Connect to Host
  • Add New SSH Host
  • Press Enter to confirm
  • Select SSH configuration file to update. This will persist connection parameters into the ./ssh/config

Connect to the configured SSH host

On the left-hand side, VSCODE shows the Remote Explorer icon, once you press on it, your connection will be listed. - Click on connect - When prompted, enter the password you copied from the Password field. This will authenticate the connection.

Once connected, VSCODE will have access to the container, where you can run commands, check logs, forward ports, and perform VSCODE development tasks as needed.

Important notes:

  • To keep connection alive, try ServerAliveInterval parameter
  • To reuse datasets, use paths under /home/aac, this persists on a user isolated data volume that is mounted in every user workload.