I am looking for information on how to launch a Docker container than can then turn around and call Docker to build other containers or launch other containers. This in and of itself is not new, recipes exist to do this from within a Linux system that hosts docker … like this …
docker run -it --name builder1 --privileged=true -v /var/run/docker.sock:/var/run/docker.sock -v /usr/bin/docker:/usr/bin/docker alpine ash (or something like this)
The problem is when you are not running a linux system, how can you then achieve the same thing from Windows?
If its not possible from windows, can I achieve this by connecting directly to docker on windows by the hyper-v kernel, and then launching the container from there? If so, how does this affect the file system? Will space for launched child containers be allocated on the Windows file system or on the native alpine file system?
Any comments or suggestions are much appreciated!