Docker Community Forums

Share and learn in the Docker community.

Docker-machine on Ubuntu 15.04 fails for virtualbox driver


(Kwolcott) #1

Hi;

I’m using Ubuntu 15.04 with Virtualbox 5.0 with docker-machine version 0.3.0.

docker-machine create --driver virtualbox dev
Creating CA: /home/kwolcott/.docker/machine/certs/ca.pem
Creating client certificate: /home/kwolcott/.docker/machine/certs/cert.pem
Image cache does not exist, creating it at /home/kwolcott/.docker/machine/cache…
No default boot2docker iso found locally, downloading the latest release…
Downloading https://github.com/boot2docker/boot2docker/releases/download/v1.7.1/boot2docker.iso to /home/kwolcott/.docker/machine/cache/boot2docker.iso…
Creating VirtualBox VM…
Creating SSH key…
Error creating machine: exit status 1
You will want to check the provider to make sure the machine and associated resources were properly removed.

What did I do wrong?

This seems to work fine when I am using my Mac.

Thanks,
Ken Wolcott
kennethwolcott@gmail.com


(Ralph Kincade) #2

just had the same thing ! could not get it to work from ubuntu running on
virtual box

where is your docker machine running ? mine it running on windows with
cygwin and git bash


(Ralph Kincade) #3

i think the issue is that the ubuntu image is not aware of the virtual box
environment. I see you did it on a mac , so that makes sense at the MAC os
can see all the virtual box utils and stuff


(Fabrice Le Coz) #4

It’s due to a deprecated parameter ‘synthcpu’ used by docker-machine v0.3.0 when creating the VM.

As workaround to fix it you will have to patch docker-machine and rebuild it, or build the last docker-machine (0.4.0-dev),

As I was checking the docker-machine sources, i saw that a fixed version ( v0.3.1 ) has been published

curl -L https://github.com/docker/machine/releases/download/v0.3.1/docker-machine_linux-amd64 > /usr/local/bin/docker-machine

(Kwolcott) #5

Update: I downloaded the 0.3.1 docker-machine and installed it. I get
further but there is still a communication problem somewhere as I get the
following:

Starting VirtualBox VM…
Starting VM…

Error creating machine: Too many retries. Last error: Maximum number
of retries (60) exceeded
You will want to check the provider to make sure the machine and
associated resources were properly removed.

So I will try deleting stuff and trying again.

Thanks,

Ken Wolcott


(Ralph Kincade) #6

I feel your pain !!:grimacing:, I have has the same kind of crap today …all
day… with virtual box , I needed it for a docker machine demo I am
giving to company in the morning but finally gave up and used Rackspace and
Digital ocean as my targets for docker machine to deploy to .


(Kwolcott) #7

More detail to the update (0.3.1 is still buggy):

docker-machine create --driver virtualbox dev
Creating CA: /home/kwolcott/.docker/machine/certs/ca.pem
Creating client certificate: /home/kwolcott/.docker/machine/certs/cert.pem
Image cache does not exist, creating it at
/home/kwolcott/.docker/machine/cache…
No default boot2docker iso found locally, downloading the latest release…
Downloading
https://github.com/boot2docker/boot2docker/releases/download/v1.7.1/boot2docker.iso
to /home/kwolcott/.docker/machine/cache/boot2docker.iso…
Creating VirtualBox VM…
Creating SSH key…
Starting VirtualBox VM…
Starting VM…
Error creating machine: Too many retries. Last error: Maximum number of
retries (60) exceeded
You will want to check the provider to make sure the machine and associated
resources were properly removed.

Thanks,
Ken Wolcott


(Frank) #8

I’m getting same error but have docker-machine -v
docker-machine version 0.4.0 (9d0dc7a)

I’m just trying to do the example https://docs.docker.com/machine/get-started/ with no luck.


(Tom Truitt) #9

this isn’t working for me 6 months later… is there a solution?


(Tom Truitt) #10

interesting:

i downgraded vb and got this error:
Error creating machine: Error in driver during machine creation: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory

so i can only assume that the issue continues into the newer version only for some reason the error isnt being presented


(Dvohra) #11

Does the system support harware virtualization? If not known use a tool such as Intel Processor Identification Utility or find from the .Intel Virtualization Technology list.


(Nathan Le Claire) #12
  1. You should always use latest VBox if at all possible
  2. Did you follow these instructions and confirm that hardware virt is enabled in the BIOS?