Diagnosis or useful alert for daemon.json broken

[yfdyh000]

Tell us about your request Diagnosis or useful tips for user's daemon.json file broken, the software quietly does not started.

Which service(s) is this request for? Docker Desktop for Windows.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? I accidentally break the C:\Users\<username>\.docker\daemon.json file while adding the "registry-mirrors" servers, it has a bad JSON. After a period of time, I tried to start the Docker Desktop again, it doesn't respond, no tray or alert. Sometimes it says Docker is exiting (meaning).

Are you currently working around the issue?

• Rename the daemon.json file, re-start it, this file is rebuilt and the product is restored.
• Use the C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe based on the doc, it collect many information and uploaded, no offline diagnostics options provided, and it only gives me a diagnostic ID (not available to the free plan), not helpful.

[nebuk89]

@yfdyh000 this is great feedback, we are currently working on some tools to help with diagnosis of issues and this is a great case we hadn't considered. I don't know if this will make it into the first release but we will 100% look at adding this to it!

[christophermclellan]

Thanks for your idea! This is something we will consider as part of our wider efforts to improve error messages within Docker Desktop. I'll add to the Considering column of our roadmap.