I second this - we also have scripts to set up our (rather large, complicated to manually setup) test environment.
Normally I would clone our GIT repository or add a shared directory from host to client to be able to execute the script(s).
Not exactly ssh but equivalent results. “Docker Saigon” solution:
#get a privileged container with access to Docker daemon
docker run --privileged -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v /usr/bin/docker:/usr/bin/docker alpine sh
#run a container with full root access to MobyLinuxVM and no seccomp profile (so you can mount stuff)
docker run --net=host --ipc=host --uts=host --pid=host -it --security-opt=seccomp=unconfined --privileged --rm -v /:/host alpine /bin/sh
When designing Docker for Windows, we weighed trade-offs between flexibility and customizability vs. dependability and determinism.
docker-machine is very flexible (there are lots of different drivers) and customizable (the setup has lots of parameters and there’s SSH access to the machines). But the experience is also very variable (not all features work with all drivers or settings) and inexperienced users can quickly get in trouble.
With Docker for Windows, we’ve tried to build a more dependable Docker environment. We know that this has come at some cost to flexibility. Your feedback is very valuable as we continue to work towards the right balance.
Thanks for your response Michael. But if you allow my 2cents on this…
DfW will inevitably be compared to the current Docker Toolbox. And I would expect that a “docker-machine create -d dfw …” to be on the horizon…
Why would that make a less dependable Docker environment? I see DfW as a dev environment replacing Virtualbox by hyperv and (hopefully) making things more robust and speedier…
I was looking for ssh access to set the http proxy. I want to be able to set the proxy for the VM since docker for windows does not work behind our corporate proxies.
Running docker images to look at the filesystem of the MobyVM is useful and educational, but still no good if you are wanting to do anything which requires restarting the docker engine. e.g. installing plugins, changing drive sizes, defaults for DNS, etc. Some of these options are in the UI…
I am running the latest beta and can see that the tray app has a UI to set some settings, which is helpful. However, in my case I some SSL certs that need to be trusted (I’m behind a transparent SSL proxy and need to trust its CA certs). Is there a way to do that?
You can already mount the Docker socket, and instead of trying to use a binary from the Moby host, you can run a container that has the Docker CLI binary in it, like this one: Docker