Just spent two solid days trying to figure out why my #dockerized #ASPNet project wouldn't publish to my #docker #registry from #VisualStudio.

Wanna take a wild guess as to the problem? Was it my code? Was it my configuration?

No. Turns out that Docker Desktop 4.3x just has a bug with Visual Studio.  That's a lot of my life I can't get back for something so stupid.

As of now, this is the only page on the internet that seems to describe the issue even in vague terms. But it was enough of a clue to try the old version, which worked.

https://forums.docker.com/t/after-rebooting-my-laptop-i-can-no-longer-public-to-azure-container-registry-happened-last-4-times-i-rebooted/142027

After rebooting my laptop, I can no longer public to Azure Container Registry. Happened last 4 times I rebooted

Hello, The last 4 times I have rebooted my computer, I can no longer publish to Azure Container Registry after the reboot. I’ve been publishing to the very same container over a 3 year period without issue until last week. The only way I’ve been able to fix it is to uninstall docker desktop for Windows then re-install. Does anyone have a fix for this? Thank you in advance. Failed to initialize: unable to resolve docker endpoint: context “desktop-linux”: context not found: open C:\Users\redacte...

Docker Community Forums