Unable to start debugging Docker container

[PawLove]

Hi! I'm trying out the Visual Studio 2017 Community and ASP.NET Core web app and get a prompt stating "Unable to start debugging. Unable to establish a connection to VSDBG. Debug output may contain more information."

Output Windows shows the following:

Starting: "docker" exec -i dd11077d4248 /clrdbg/vsdbg/vsdbg --interpreter=mi
rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "exec: "/clrdbg/vsdbg/vsdbg": stat /clrdbg/vsdbg/vsdbg: no such file or directory"
"docker" exited with code 126 (0x7E).

I saw that a similar problem was being discussed
dotnet/dotnet-docker#162
But the solution did not help.

Steps to reproduce the issue

1.Open VS 2017 Community
2.Create new ASP.NET Core Web App
3.Debug with Docker

Expected behavior

Should run app in container and allow breakpoints, etc.

Actual behavior

It prompts with error mentioned above. It does appear to deploy and run a container.

Output of docker version

Client:
Version: 17.03.1-ce
API version: 1.27
Go version: go1.7.5
Git commit: c6d412e
Built: Tue Mar 28 00:40:02 2017
OS/Arch: windows/amd64

Server:
Version: 17.03.1-ce
API version: 1.27 (minimum version 1.12)
Go version: go1.7.5
Git commit: c6d412e
Built: Fri Mar 24 00:00:50 2017
OS/Arch: linux/amd64
Experimental: true

Output of docker info

Containers: 4
Running: 1
Paused: 0
Stopped: 3
Images: 12
Server Version: 17.03.1-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 4.9.27-moby
Operating System: Alpine Linux v3.5
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.934 GiB
Name: moby
ID: 2NIF:L7XL:JNC7:UIWV:VCGX:KBZU:MITL:43VJ:X3VR:DWKL:BZAO:TXP6
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 21
Goroutines: 32
System Time: 2017-05-22T17:19:35.5988348Z
EventsListeners: 0
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

[kokoska69]

See output from build if there are not any errors.

[ivan-danilov]

Same issue here

[Emill]

Same issue here. No errors in Build output what I can see:

1>------ Build started: Project: docker-compose, Configuration: Debug Any CPU ------
1>docker-compose -f "C:\Users\Emil\Documents\Visual Studio 2017\Projects\WebApplication1\docker-compose.yml" -f "C:\Users\Emil\Documents\Visual Studio 2017\Projects\WebApplication1\docker-compose.override.yml" -f "C:\Users\Emil\Documents\Visual Studio 2017\Projects\WebApplication1\docker-compose.vs.debug.yml" -p dockercompose4136979918 config
1>networks: {}
1>services:
1>  webapplication1:
1>    build:
1>      args:
1>        source: obj/Docker/empty/
1>      context: C:\Users\Emil\Documents\Visual Studio 2017\Projects\WebApplication1\WebApplication1
1>      dockerfile: Dockerfile
1>    entrypoint: tail -f /dev/null
1>    environment:
1>      ASPNETCORE_ENVIRONMENT: Development
1>      DOTNET_USE_POLLING_FILE_WATCHER: '1'
1>    image: webapplication1:dev
1>    labels:
1>      com.microsoft.visualstudio.targetoperatingsystem: linux
1>    ports:
1>    - '80'
1>    volumes:
1>    - C:\Users\Emil\Documents\Visual Studio 2017\Projects\WebApplication1\WebApplication1:/app:rw
1>    - C:\Users\Emil\clrdbg:/clrdbg:ro
1>    - C:\Users\Emil\.nuget\packages:/root/.nuget/packages:ro
1>version: '2.0'
1>volumes: {}
1>docker  ps --filter "status=running" --filter "name=dockercompose4136979918_webapplication1_" --format {{.ID}} -n 1
1>7c26a1794612
1>docker  exec -i 7c26a1794612 /bin/bash -c "if PID=$(pidof -x dotnet); then kill $PID; fi"
1>WebApplication1 -> C:\Users\Emil\Documents\Visual Studio 2017\Projects\WebApplication1\WebApplication1\bin\Debug\netcoreapp1.1\WebApplication1.dll
1>C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NonInteractive -NoProfile -WindowStyle Hidden -ExecutionPolicy RemoteSigned -File "C:\Users\Emil\AppData\Local\Temp\GetVsDbg.ps1" -Version vs2017u1 -RuntimeID debian.8-x64 -InstallPath "C:\Users\Emil\clrdbg\vsdbg"
1>Info: Using vsdbg version '15.1.10502.1'
1>Info: Using Runtime ID 'debian.8-x64'
1>Info: Latest version of VsDbg is present. Skipping downloads
1>docker-compose -f "C:\Users\Emil\Documents\Visual Studio 2017\Projects\WebApplication1\docker-compose.yml" -f "C:\Users\Emil\Documents\Visual Studio 2017\Projects\WebApplication1\docker-compose.override.yml" -f "C:\Users\Emil\Documents\Visual Studio 2017\Projects\WebApplication1\docker-compose.vs.debug.yml" -p dockercompose4136979918 up -d
1>dockercompose4136979918_webapplication1_1 is up-to-date
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========

Debug output:

Starting: "docker" exec -i 7c26a1794612 /clrdbg/vsdbg/vsdbg --interpreter=mi
rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "exec: \"/clrdbg/vsdbg/vsdbg\": stat /clrdbg/vsdbg/vsdbg: no such file or directory"
"docker" exited with code 126 (0x7E).

[radulacatus]

i had the same issue
for me it worked running docker for windows as admin

[Emill]

I installed vs2017 update 3 preview and now it works.

[pwasiewicz]

Same here. But none of both helped: running doker daemon as admin nor installing vs2017 preview 3.

[kenpavia]

I was getting this error while on a vpn. I jumped off the vpn and the debug error went away (after a reboot). Now, I have to figure out why being on a vpn causes the problem.

[liqdfire]

I have my machine joined to an Azure AD, and my windows login is my AAD account, not a local account.
I had to create a local user account for sharing drive in docker; however, the docker tools in VS2017 use the profile directory of the logged in user as the path for clrdbg and .nuget, which the local account would not have access to.

See this issue for other symptoms
docker/for-win#898

To resolve it, I have to give the local user account that I am using to share drive in docker, read access to my logged in user profile directory. You will need read and write if you are using the default git repo folder of source\repos under y our profile directory.

[bwateratmsft]

This issue is being closed as an inactive issue. If you wish to keep it active, please re-open with any additional context for our consideration, we are happy to take a look!