Depending upon the network speed and restrictions, you may not be able to download Docker images from Docker Store. The error message may look like:
$ docker pull arungupta/wildfly-mysql-javaee7
Using default tag: latest
Pulling repository docker.io/arungupta/wildfly-mysql-javaee7
Network timed out while trying to connect to https://index.docker.io/v1/repositories/arungupta/wildfly-mysql-javaee7/images. You may want to check your internet connection or if you are behind a proxy.
This section provide a couple of alternatives to solve this.
Are you not able to create Docker Machine on Windows?
Try starting a cmd
with Administrator privileges and then give the command again.
If you get the following error when creating a docker machine
Error creating machine: Error in driver during machine creation: Get https://api.github.com/repos/boot2docker/boot2docker/releases: dial tcp: i/o timeout
Then you need to go to the boot2docker releases page on
And download the latest .iso
After that you can move that iso to the docker cache directory. This is located in ~/.docker/machine/cache
on Mac & Linux and /Users/yourUserName/.docker/machine/cache
on Windows.
Issue: docker/machine#2186 is raised so that the docker-machine team can hopefully find a way around this.
In order to create
or upgrade
virtual machines running Docker, Docker
Machine will check the Github API for the latest release of the [boot2docker
operating system](https://github.com/boot2docker/boot2docker). The Github API
allows for a small number of unauthenticated requests from a given client, but
if you share an IP address with many other users (e.g. in an office), you may
get rate limited by their API, and Docker Machine will error out with messages
indicating this.
In order to work around this issue, you can generate a
token and pass it to Docker Machine using the global --github-api-token
flag:
$ docker-machine --github-api-token=token create -d virtualbox newbox
This should eliminate any issues you’ve been experiencing with rate limiting.
Docker Machine Troubleshooting section has good tips on what can possibly go wrong with Docker Machine. Look there if your issue is not explained here.