vscode: Can't attach Node.js debugger to hostname any more

Issue Type: Bug

I used to be able to attach to a Docker-base Node.js debug instance with the following launch config:

        {
          "type": "node",
          "request": "attach",
          "name": "Attach to Docker API",
          "port": 9229,
          "address": "api.docker",
          "localRoot": "${workspaceFolder}",
          "remoteRoot": "/app",
          "protocol": "inspector",
          "sourceMaps": true,
          "restart": true,
          "skipFiles": [
            "main.js",
            "async_hooks.js",
            "*.js",
          ]
        },

This no longer works, the only way I could get it working was by specifying the container IP, e.g. "address": "172.17.0.8",. Disabling all extensions doesn’t help either.

This is a little problematic since the container IP may not be preserved between re-launches.

VS Code version: Code 1.22.2 (3aeede733d9a3098f7b4bdc1f66b63b0f48c1ef9, 2018-04-12T16:32:53.389Z) OS version: Darwin x64 17.3.0

System Info

Item	Value
CPUs	Intel® Core™ i7-4770HQ CPU @ 2.20GHz (8 x 2200)
Load (avg)	3, 3, 3
Memory (System)	16.00GB (0.14GB free)
Process Argv	/Applications/Visual Studio Code.app/Contents/MacOS/Electron
Screen Reader	no
VM	0%

Extensions (18)

Extension	Author (truncated)	Version
swagger-viewer	Arj	1.6.0
EditorConfig	Edi	0.12.1
gc-excelviewer	Gra	2.0.20
beautify	Hoo	1.3.0
material-icon-theme	PKi	3.3.0
vscode-docker	Pet	0.0.26
fish	Ted	0.0.4
vscode-intelephense-client	bme	0.8.8
gitlens	eam	8.2.4
tslint	eg2	1.0.28
ansible	haa	0.2.8
terraform	mau	0.0.23
python	ms-	2018.3.1
sublime-keybindings	ms-	3.0.3
vscode-yaml	red	0.0.11
vscode-nginx	sha	0.5.0
ansible-autocomplete	tim	0.0.2
jinja	who	0.0.8