The instructions (https://docs.docker.com/engine/installation/windows/) to install Docker on Windows is more complex than install gcc tool chain and make utils. It even requires to check VT support of your CPU!! Also, if you want to invoke Docker from command-line, you need to edit PATH variable-- why not add gcc and make to PATH instead? And then you are ready to go.
I also noticed that Docker creates VirtualBox VM on Windows to "implement" LXC on Windows. Please correct me if I were wrong. If it is the case, why not create a well setup Linux development VM image and distribute it to everyone who is interested in compiling AQ himself? The TauLabs project is doing so: https://github.com/TauLabs/TauLabs/wiki ... al-machine
IMO the use of virtualization brings more problems than benefits to embedded debugging. Have you tried to debug in a Docker environment? How does the ST-Link or J Link debugger works with it? Is the driver working or not?
The last thing a newcomer wants is following steps seems very simple, but at last turned out to have lots of problems. It is far more frustrating than spend one day configuring dev env.
I've consulted with one friend who actually has Docker deployed in production. It is used to deploy some web-based applications, and I believe that is what Docker is designed for. In that scenario, Docker can solve dependencies issues like OS/AppServer or DB. So probably you could look into building AQ GCS with Docker. As we know, QGC requires several trouble making libs, e.g. the tts. It would be nice if these issues can be resolved.