search

microsoft / vscode-docker

Docker Extension for Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-docker
Other
1.19k stars 508 forks source link

Docker Resource Saver causes poor UX in .NET SDK Publishing #4171

Closed baronfel closed 6 months ago

baronfel commented 7 months ago

On Docker for Windows, if the Resource Saver feature kicks in then .NET SDK Container Publish + Debugging doesn't trigger successfully. What happens is that the user can select the "Debug in container" => "Use .NET SDK" flow, but after that the UI just....stays in a 'pending' state forever. There's no log activity in the Docker Output channel, and overall the user has no indication of what the problem is. Once you kick the Resource Saver feature by using the Docker CLI in some way, then the Docker extension comes back to life.

bwateratmsft commented 7 months ago

I ended up disabling the resource saver.

bwateratmsft commented 7 months ago

@baronfel is the SDK build what is hanging indefinitely or something else?

baronfel commented 7 months ago

From what I can see the SDK build isn't even being triggered (the Task output pane that I would usually see is never even created). I suspect there's some Docker interaction/probing happening in the VSCode Docker tooling before launching the SDK build, but I'm not certain.

bwateratmsft commented 7 months ago

I was not able to reproduce this when I tried. Does it reproduce consistently for you @baronfel?

I was on a new RC build of Docker Desktop so it's possible it contains improvements to the resource saver's wake-up sequence

Update: Docker Desktop 4.25.2 also did not reproduce

AzCode-Bot commented 6 months ago

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!