Public | Automated Build

Last pushed: 2 years ago
Short Description
docker machine.
Full Description

Docker Machine

Machine lets you create Docker hosts on your computer, on cloud providers, and
inside your own data center. It creates servers, installs Docker on them, then
configures the Docker client to talk to them.

It works a bit like this:

$ docker-machine create -d virtualbox dev
Creating CA: /home/username/.docker/machine/certs/ca.pem
Creating client certificate: /home/username/.docker/machine/certs/cert.pem
Image cache does not exist, creating it at /home/username/.docker/machine/cache...
No default boot2docker iso found locally, downloading the latest release...
Downloading https://github.com/boot2docker/boot2docker/releases/download/v1.6.2/boot2docker.iso to /home/username/.docker/machine/cache/boot2docker.iso...
Creating VirtualBox VM...
Creating SSH key...
Starting VirtualBox VM...
Starting VM...
To see how to connect Docker to this machine, run: docker-machine env dev

$ docker-machine ls
NAME   ACTIVE   DRIVER       STATE     URL                         SWARM
dev    *        virtualbox   Running   tcp://192.168.99.127:2376

$ eval "$(docker-machine env dev)"

$ docker run busybox echo hello world
Unable to find image 'busybox:latest' locally
511136ea3c5a: Pull complete
df7546f9f060: Pull complete
ea13149945cb: Pull complete
4986bf8c1536: Pull complete
hello world

$ docker-machine create -d digitalocean --digitalocean-access-token=secret staging
Creating SSH key...
Creating Digital Ocean droplet...
To see how to connect Docker to this machine, run: docker-machine env staging

$ docker-machine ls
NAME      ACTIVE   DRIVER         STATE     URL                          SWARM
dev                virtualbox     Running   tcp://192.168.99.127:2376
staging   *        digitalocean   Running   tcp://104.236.253.181:2376

Installation and documentation

Full documentation is available here.

Contributing

Want to hack on Machine? Please start with the Contributing Guide.

Troubleshooting

Docker Machine tries to do the right thing in a variety of scenarios but
sometimes things do not go according to plan. Here is a quick troubleshooting
guide which may help you to resolve of the issues you may be seeing.

Note that some of the suggested solutions are only available on the Docker
Machine master branch. If you need them, consider compiling Docker Machine from
source. There are also unofficial pre-compiled master
binaries
hosted by
@ehazlett.

docker-machine hangs

A common issue with Docker Machine is that it will hang when attempting to start
up the virtual machine. Since starting the machine is part of the create
process, create is often where these types of errors show up.

A hang could be due to a variety of factors, but the most common suspect is
networking. Consider the following:

  • Are you using a VPN? If so, try disconnecting and see if creation will
    succeed without the VPN. Some VPN software aggressively controls routes and
    you may need to manually add the route.
  • Are you connected to a proxy server, corporate or otherwise? If so, take a
    look at the --no-proxy flag for env and at setting environment variables
    for the created Docker Engine
    .
  • Are there a lot of host-only interfaces listed by the command VBoxManage list hostonlyifs? If so, this has sometimes been known to cause bugs. Consider
    removing the ones you are not using (VBoxManage hostonlyif remove name) and
    trying machine creation again.

We are keenly aware of this as an issue and working towards a set of solutions
which is robust for all users, so please give us feedback and/or report issues,
workarounds, and desired workflows as you discover them.

Machine creation errors out before finishing

If you see messages such as "exit status 1" creating machines with VirtualBox,
this frequently indicates that there is an issue with VirtualBox itself. Please
file an issue and include a link
to a Github Gist with the output of the VirtualBox
log (usually located at
$HOME/.docker/machine/machines/machinename/machinename/Logs/VBox.log), as well
as the output of running the Docker Machine command which is failing with the
global --debug flag enabled. This will help us to track down which versions
of VirtualBox are failing where, and under which conditions.

If you see messages such as "exit status 255", this frequently indicates there
has been an issue with SSH. Please investigate your SSH configuration if you
have one, and/or file an issue.

"You may be getting rate limited by Github" error message

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
. 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 like
so:

$ docker-machine --github-api-token=token create -d virtualbox newbox

This should eliminate any issues you've been experiencing with rate limiting.

Docker Pull Command
Owner
xprayc
Source Repository

Comments (0)