Skip to content
Branch: master
Find file Copy path
3 contributors

Users who have contributed to this file

@andyneff @pieandcakes @faheel
55 lines (44 sloc) 2.1 KB

Pipe Transport

Pipe Transport allows communication through a pipe program to a remote shell. An example on Linux would be ssh.


We have added "pipeTransport" as an option within the launch.json file. The structure looks as follows:

"pipeTransport": {
    "pipeCwd": "/usr/bin",
    "pipeProgram": "/usr/bin/ssh",
    "pipeArgs": [
    "debuggerPath": "/usr/bin/gdb"

The pipeArgs can be any set of arguments necessary to setup and authenticate the pipe connection. In the example, a password is used but you can also use an ssh key.

You may also need to add a sourceFileMap to map the path of where the code exists on the remote shell to where it is locally:

"sourceFileMap": {
    // "remote": "local"
    "/home/user/src": "/src/projectA/src"


You can also use the above pipeTransport block to attach to a remote process. In the attach case, you will need to specify a processId. We have added the ability to query processes from the remote machine. To do this, change "processId": "${command.pickProcess}" to "processId": "${command.pickRemoteProcess}". The pipeTransport settings will be used to query the processes on the remote machine. Then select the process from the drop down list. As with launch, you may need to configure sourceFileMap.

Docker example

The pipeTransport can also be used to debug a process in a Docker container. For an attach, launch.json will include:

"pipeTransport": {
    "pipeCwd": "${workspaceRoot}",
    "pipeProgram": "docker",
    "pipeArgs": [
    "debuggerPath": "/usr/bin/gdb"

Where hello_gdb is the name of your container.

Launching a process is accomplished by starting a container and then using the same pipeTransport launch additional processes in the container. See this launch.json for a full example.

You can’t perform that action at this time.