[Question] Debugging Docker with this workflow?

sesispla / docker-nginx-kestrel

A basic ASP.NET Core App, Dockerized and served with NGINX as proxy server.

MIT License

67 stars 26 forks source link

[Question] Debugging Docker with this workflow? #1

Open MarkPieszak opened 7 years ago

MarkPieszak commented 7 years ago

Hey @sesispla I was just wondering, so considering this is all in a solution together.

Is a Dev supposed to be running all of this within Docker (.NET Core app, Nginx) and debugging it that way? Let's say there were many other layers, micro-services, etc as well, that needed to be setup with Docker.

New-ish to the Docker world, just wondering how one goes about debugging and developing in this workflow. Thanks for any input :+1:

sesispla commented 7 years ago

Hello @MarkPieszak. First of all, sorry for the long delay in responding.

AFAIK you can now debug Docker container using Visual Studio 2017 and Docker support.

I am going to make an small improvement to make the current code to work again. Then I'll check if is possible to mix this solution with latest VS2017 Tooling bits.

dmarlow commented 6 years ago

I too am interested. I tried debugging and got a strange error in VS:

1>Target DockerCreateComposeVsGeneratedFiles:
1>  C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Sdks\Microsoft.Docker.Sdk\build\Microsoft.VisualStudio.Docker.Compose.targets(281,5): error : (Line: 5, Col: 12, Idx: 46) - (Line: 5, Col: 17, Idx: 51): Exception during deserialization
1>Done building target "DockerCreateComposeVsGeneratedFiles" in project "docker-compose.dcproj" -- FAILED.

I'm replacing the docker-compose.yml contents of the generated template that comes from VS.

sesispla commented 6 years ago

@dmarlow VS2017 docker-compose files are a bit tricky. No straight way to copy/paste them and make this solution to work in a fast way :).

Need to review it and prepare some sort of patch for VS2017+