From e0b00b16b615dbdb468df644410655d13ac296b0 Mon Sep 17 00:00:00 2001 From: Christof Marti Date: Mon, 8 Mar 2021 15:41:09 +0100 Subject: [PATCH] Doc Remote-Containers version --- remote-release-notes/v1_54.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/remote-release-notes/v1_54.md b/remote-release-notes/v1_54.md index 28230ef2c..56b8e2153 100644 --- a/remote-release-notes/v1_54.md +++ b/remote-release-notes/v1_54.md @@ -24,7 +24,7 @@ Extension sometimes listen on a port from within the VS Code remote extension ho By default, VS Code will find ports to automatically forward for you by looking at the currently running processes on the remote system. In some cases, this is not desirable. To help with those cases, there is now the setting `remote.autoForwardPortsSource`. To look for ports to forward based on terminal and debug output (instead of running processes) set `"remote.autoForwardPortsSource": "output"`. Note that ports auto forwarded from an `output` source will not be closed when the process stops running. -## Containers +## Containers (version 0.163.x) ### portsAttributes setting in devcontainer.json