I’m trying to run a docker container on a windows amazon ec2 server but I’m running into problems. I don’t think the installation can access localhost when I try to do boot2docker up. Are there any alternatives to boot2docker for windows or is there some way I can circumvent this problem?
For example, trying to do boot2docker -v up yields .Connecting to tcp://localhost:2022 (attempt #0) over and over again.
docker version gives Client version: 1.7.1 Client API version: 1.19 Go version (client): go1.4.2 Get http://127.0.0.1:2375/v1.19/version: dial tcp 127.0.0.1:2375: ConnectEx tcp: No connection could be made because the target machine actively refused it.. Are you trying to connect to a TLS-enabled daemon without TLS?
Is docker-machine an alternative to this? I’ve tried installing the docker-machine binary for win64bit but it doesn’t work. cURL installing also doesn’t actually install anything in the target folder but I’m not sure if these problems (w/the localhost one) are linked.
Can you confirm if the “boot2docker-vm” VM has started successfully?
To check this, you can bring up the Oracle VM VirtualBox Manager GUI app and look for the status of the “boot2docker-vm” VM.
It is quite possible that the VM itself has not started, in which case, you will have to debug that first.
If it has started, then the problem is with the Docker daemon. Again, it is quite possible that the Docker daemon did not start successfully in the “boot2docker-vm” VM.
The Docker Client details that you see above are about the Windows Docker Client that has been installed and working well. It is not the Docker Client on the “boot2docker-vm” VM.
And let me try to answer your questions:
Are there any alternatives to boot2docker for windows or is there some way I can circumvent this problem?
Ans: I do no think there is any alternative to boot2docker for Windows at this time. Docker Inc., folks, please confirm this. And there is no way to circumvent this issue. But I think this can be solved by debugging.
Is docker-machine an alternative to this?
Ans: My guess is that, if you can’t get “boot2docker” to work, you won’t be able to get docker-machine to create Docker hosts on your Amazon EC2 Windows instance.
boot2docker-vm says running in the VBox GUI, so it has started successfully (surprisingly unlike in windows access)
How would I go about debugging this if it isn’t a vbox issue? I have a feeling that it has something to do with internet or localhost access, mainly because of the attempt to connect to localhost. When vbox isn’t running properly I see an error like it starts and then it exits immediately afterwords with some status code.
Since vbox is working I thought docker-machine should be able to create docker hosts, but cURL installing it doesn’t work which is the only way available right now according to the docs for windows, leading me to think the two issues are linked. Because yes, you’re right I think. If it isn’t an issue with Vbox then there’s something else under the hood that’s debuggable, I think.
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d
OS/Arch (client): windows/amd64
Get http://127.0.0.1:2375/v1.19/version: dial tcp 127.0.0.1:2375: ConnectEx tcp: No connection could be made because thetarget machine actively refused it.. Are you trying to connect to a TLS-enabled daemon without TLS?
When I look at the VBox manager, I see that in the preview for the VM the boot2docker whale thing shows up. The virtual machine says “running”, Linux 2.6/3.x (64-bit)