docs: add MCP Server JSON configuration for Docker Engine in WSL

[bartkol]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.

---

Description

Adds JSON MCP server configuration in case one is using Docker Engine installed inside WSL. Not everyone can or want to use Docker Desktop and provided configuration at the moment doesn't work without tweaking. Change to doc helps people use Awesome Copilot without docker knowledge or the need of configuring docker command.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• Update to existing instruction, prompt, agent, plugin, skill, or workflow.
• Other (please specify): updating README.md

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[aaronpowell]

I don't understand this, why would you launch WSL to then run Docker, rather than using Docker natively from Windows? Is this to tackle the scenario where someone is only installing Docker under WSL so it runs only within a Linux environment? That's a rather inefficient way to run Docker on Windows as it won't take advantage of native acceleration.

[bartkol]

I don't understand this, why would you launch WSL to then run Docker, rather than using Docker natively from Windows? Is this to tackle the scenario where someone is only installing Docker under WSL so it runs only within a Linux environment? That's a rather inefficient way to run Docker on Windows as it won't take advantage of native acceleration.

Docker doesn't run natively on Windows even when Docker Desktop is installed. Docker Desktop's docker.exe client gives that illusion by forwarding commands to Docker Engine that lives in WSL2.

To use Docker Desktop one has to get a license. Of course Docker Desktop is free for personal use, but not for commercial use. Installing Docker Engine on WSL is very good alternative to still use Docker for free. Rancher Desktop works just the same - Docker Engine still lives inside WSL.

Using docker commands is exactly the same as using wsl docker commands from powershell or using docker commands inside wsl.

[aaronpowell]

I'm going to close this for the moment because we're about to undertake a large refactor of the README to simplify it and better integrate with the website.