question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Debugging .NET Core inside a Docker Container from Windows host - Error: Input connection was closed. Aborting the debug session.

See original GitHub issue

Environment data

dotnet --info output:

.NET Command Line Tools (2.0.0)

Product Information:
 Version:            2.0.0
 Commit SHA-1 hash:  cdcd1928c9

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.15063
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.0.0\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

VS Code version: image

C# Extension version: 1.12.1

Docker for Windows version: Version 17.06.1-ce-win24 (13025)

Steps to reproduce

I have pushed a test repo to GitHub here - https://github.com/lewislabs/test_debug/ Clone this repo and follow the steps for running the app in the readme here

Expected behavior

The application starts up and the breakpoint is hit.

Actual behavior

I get the following output in the debug console and an error popup in VS Code.

Starting: "docker" exec -i test-debug /vsdbg/vsdbg --interpreter=vscode
-> (C) {"command":"initialize","arguments":{"clientID":"vscode","adapterID":"coreclr","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true},"type":"request","seq":1}
Error from pipe program 'docker': Error: Input connection was closed. Aborting the debug session.
<- (ERROR) {"request_seq":2,"success":false,"command":"launch","message":"The pipe program 'docker' exited unexpectedly with code 0.","body":{"error":{"id":1000,"format":"The pipe program 'docker' exited unexpectedly with code 0."}},"seq":1,"type":"response"}

Issue Analytics

  • State:open
  • Created 6 years ago
  • Comments:13 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
damturcommented, Dec 11, 2017

See https://github.com/Maximus5/ConEmu/issues/1068 as well

Also when running on bash, in cmder setting ConEmuANSI doesn’t help

1reaction
WardenGnawcommented, Sep 6, 2017

It may be an issue with ConEmu. One work around to get VsCode working with Cmder is running set ConEmuANSI=OFF before launching VsCode.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Debugging .NET Core inside a Docker Container from Windows ...
Debugging .NET Core inside a Docker Container from Windows host - Error: Input connection was closed. Aborting the debug session.
Read more >
Unable to Connect to the Microsoft Visual Studio Remote ...
This message may occur because the remote debugging monitor is not properly set up on the remote machine or the remote machine is...
Read more >
How do I debug error ECONNRESET in Node.js?
You might have guessed it already: it's a connection error. "ECONNRESET" means the other side of the TCP conversation abruptly closed its end...
Read more >
APM Connection Errors - Datadog Docs
If the application with the tracing library cannot reach the Datadog Agent, look for connection errors in the tracer startup logs or tracer...
Read more >
How to Fix and Debug Docker Containers Like a Superhero
Container errors are tricky to diagnose, but some investigative magic works wonders. Read along to learn how to debug Docker containers.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found