[Feature Request] Specify a static IP for VirtualBox VMs

[letsgolesco]

Hi, I've been searching through the docs and issues to figure this out but can't find an answer.

Basically, I want to be able to specify the IP address of a VM (i.e. the value that's listed under "URL" in docker-machine ls) when I create it with docker-machine create.

I want this because I've been relying on boot2docker's default address of 192.168.59.103, but now it varies from machine to machine.

Thanks!

[hanks]

+1, need this feature

[krancour]

+1

[jsuksl]

+1

[FlorianLoch]

+1

[krancour]

Here's a good workaround. Add the following to your ~/.bash_profile:

eval `docker-machine env <docker-machine name>`
export <some variable>=$(docker-machine ip <docker-machine name>)

[luislavena]

@letsgolesco you can use --virtualbox-hostonly-cidr option for that, which will select the proper vboxnetX host-only adapter.

By default, seems docker-machine picks one randomly, so forced to use the one for vboxnet0 (192.168.59.3/24, the one used by boot2docker) seems to solve the issue:

$ docker-machine create --driver virtualbox --virtualbox-hostonly-cidr "192.168.59.3/24" dev
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 ip dev
192.168.59.103

Cheers.

[krinkere]

@luislavena - Unfortunately that did not work.

[krinkere]

+1

Def need this feature though!

[luislavena]

@krinkere not sure your env, but this worked for my OSX installation by doing that, but failed when using machine on Linux, which required tweaks to dhcpserver configuration of vboxnet0:

$ VBoxManage dhcpserver modify --ifname vboxnet0 --disable

$ VBoxManage dhcpserver modify --ifname vboxnet0 --ip 192.168.59.3 --netmask 255.255.255.0 --lowerip 192.168.59.103 --upperip 192.168.59.203

$ VBoxManage dhcpserver modify --ifname vboxnet0 --enable

$ docker-machine create --driver "virtualbox" --virtualbox-cpu-count "-1" --virtualbox-disk-size "30000" --virtualbox-memory "2560" --virtualbox-hostonly-cidr "192.168.59.3/24" dev

This is, as you can see, a huge hack 😸, but works for now 😄

[joaquinmoreira]

Would love to see this feature!!

[krinkere]

@luislavena - Thanks for your response

Here is what I get on my Mac.

$ docker-machine create --driver virtualbox --virtualbox-hostonly-cidr "192.168.99.3/24" dev
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 ip dev
192.168.99.100

While I do have ip in the right subnet, it is not the IP that I would want to use... Def would love to see this feature

[Kaycell]

+1 usefull feature

[jwebb-va]

+1 This feature would really help us out!

We use docker-machine to run a local Elasticsearch cluster and we have /etc/hosts entry for 192.168.59.103 which maps to elastic-local.mycompany.com. Since we have moved over to docker-machine from boot2docker, we have had to continuously manually update this hosts file entry to whatever is the new IP assigned to our docker VM. We could write some automation which would update this hosts file entry for us but it would be much simpler if docker-machine just let us use a configurable IP address for new machines.

[regisxu]

+1

[wateryoma]

+1

[florrain]

+1

[fjallot]

+1

[davideuler]

+1

[alekzvik]

+1

[Kroisse]

+1

[ardydedase]

+1

[oprearocks]

+1

[ianlintner-wf]

+1

[simeonpashley]

+1 (y)

[MRylander]

+1

[nh]

+1

[gvisniuc]

+1

[tombusby]

I'm all for spamming the subscribers. Some of those subscribers are part of the project team.

…

On 26 Jan 2017 14:20, "Sergey Nevmerzhitsky" ***@***.***> wrote: No need to spam the subscribers. You can unsubscribe. [image: 1] <https://cloud.githubusercontent.com/assets/1006042/22332699/4cf1a8b4-e3e3-11e6-8bad-52406c3b8055.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1709 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG44NZ2KdnsH6JTU6iI_5Uieh9WZxWXBks5rWJ2RgaJpZM4FsQYg> .

[nathanleclaire]

I'm all for spamming the subscribers.
Some of those subscribers are part of the project team.

Maintainer checking in. Please do not do spam the issue with +1 comments. This is a well known issue and spamming the thread doesn't do any good. Indicate support through the "+1" emoji reactions if you'd like. As always, we're happy to evaluate pull requests or detailed proposals. Thanks all.

(As a side note, @twang2218 seems to have the right idea generally -- static IPs are trickier than they look to get right and hit the use cases subscribers to this thread might have in mind -- perhaps an issue could be started in the boot2docker repo to discuss.)

[aniljose72]

I do not really want a static ip. But once the ip address is picked during creation, it should keep it on subsequent restarts. Is this already available?

[desimaniac]

I had a docker with VPN and the standard 192.168.99.100 wasn't loading. I figured this was because of the VPN connection, so I setup a bridge network inside Virtualbox to access the docker via 192.168.1.159. I would like this to show up on Kitematic's published IP address. Is there any way to do so?

[joelhandwell]

For those who can not wait this feature to be implemented, assigning custom ip, plus custom cpu/memory is possible by using Vagrant VirtualBox provider and docker-machine generic driver.

For example in windows, place this Vagrantfile:

Vagrant.configure("2") do |config|
  config.vm.box = "AlbanMontaigu/boot2docker"
  config.vm.provider "virtualbox" do |v|
    v.memory = 8192
    v.cpus = 8
  end
  config.vm.synced_folder ".", "/vagrant", disabled: true
  config.vm.synced_folder "C:/Users", "/c/Users"
  config.vm.network "private_network", ip: "192.168.99.103"
end

and place vagrant default ssh private key with name vagrant.pem

and run

vagrant up
docker-machine create --driver generic --generic-ip-address=192.168.99.103 --generic-ssh-user=docker --generic-ssh-key=vagrant.pem default
docker-machine ls

and you'll get docker host with custom ip, cpu, memory etc configured via vagrant at the same time accessible via docker-machine.

You can find working file set for Windows in https://github.com/joelhandwell/dockerhost

[ahilbig]

@jcwilson Hi Josh et al, thanks a lot.. I forked your script in order to fix the same issue (see minishift/minishift#343 , minishift/minishift#598) in combination with minishift:

https://github.com/ahilbig/docker-machine-ipconfig

[mahnunchik]

Any news?

[gbraad]

Currently, I am experimenting with this for Minishift: minishift/minishift#1293
Although, another approach would be to use something like cloud-init (which is maybe to heavy for this approach, or embed a DHCP server inside the Go-based binary and use this to force an allocated IP address)

[D33M]

+1.
Currently having more than one machine is horrific pain. If you use additional certificates (for example, for custom docker repository) and change order of starting machines, you have to do:

Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.100:2376"
: x509: certificate is valid for 192.168.99.101, not 192.168.99.100

This forces you to regenerate certificates or disable all machines and restore order of executing (what sometimes can be painful, too).

Additionally, using Chef to configure Docker-based project would also be much better if you could assume created machine would have always the same IP (for example, adding it to hosts file and you could forget about IPs).

[asishtom]

+1

[tnguven]

+1

[luizhpriotto]

+1
thx jcwilson, the script docker-machine-ipconfig is very good! i needed to alter the eth1 to eth0 in the script, after this, the script working perfect for me. I'm use vmware vsphere.

bye.

[vanhoutenbos]

+1

[gbraad]

As part of minishift, we have implemented minishift/minishift#1316 and this has been working well so far. We are now looking into alternatives to do the same for the other hypervisors over time, but first we will fix the address using minishift/minishift#1457 (to prevent a new address from being assigned). We haven't been able to reserve time yet, we are going to land this in minikube too.

[amoussa78]

+1

[maciekkreft]

The simplest workaround which I found is to rely on sequence of starting virtual machines by doker-machine.

VirtualBox has DHCP server which starts assigning IP adresses from 192.168.99.100.

1. Stop all VMs
   docker-machine stop ${docker-machine ls -q}
   This step will release all assigned addresses to VirtualBox DHCP

2. Start VMs in order
   docker-machine start vbox1 && docker-machine start vbox2 && docker-machine start vbox3
   This steps assign IP like this:
   192.168.99.100 : vbox1
   192.168.99.101 : vbox2
   192.168.99.102 : vbox3

Notice that docker-machine start vbox1 vbox2 vbox3 will not work, but I don't figure out why.

[provodok]

+1

[fcying]

when i run docker-machine.exe start, it takes more than 15 sec for DHCP waiting for an IP(if internet is broken, it takes more than 2minutes), i think if can set a static ip, it can boot fast.

[gbraad]

This functionality has been added to Minishift spome time ago, but it needs a modification to the ISO to function. On Hyper-V we ran into issues that the boot2docker image does not played nicely... so it only worked on CentOS and Fedora based images. Also, this does not work with the current KVM driver as it relies on DHCP. This would need a slight redesign...

…

On Sun, Feb 3, 2019 at 11:08 PM fcying ***@***.***> wrote: when i run docker-machine.exe start, it takes more than 15 sec for DHCP waiting for an IP(if internet is broken, it takes more than 2minutes), i think if can set a static ip, it can boot fast. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

-- Gerard Braad | http://gbraad.nl [ Doing Open Source Matters ]

[arikw]

The simplest workaround which I found is to rely on sequence of starting virtual machines by doker-machine.

VirtualBox has DHCP server which starts assigning IP adresses from 192.168.99.100.

1. Stop all VMs
   docker-machine stop ${docker-machine ls -q}
   This step will release all assigned addresses to VirtualBox DHCP
2. Start VMs in order
   docker-machine start vbox1 && docker-machine start vbox2 && docker-machine start vbox3
   This steps assign IP like this:
   192.168.99.100 : vbox1
   192.168.99.101 : vbox2
   192.168.99.102 : vbox3

Notice that docker-machine start vbox1 vbox2 vbox3 will not work, but I don't figure out why.

Sometimes I had to kill VBoxNetDHCP.exe process on Windows, to make vbox assign IPs starting from 192.168.99.100
Otherwise, vbox would not release IPs used by previous machines (not sure why)

[wontheone1]

👍

[wontheone1]

It would really make my life easier.

[burtsevyg]

The simplest workaround which I found is to rely on sequence of starting virtual machines by doker-machine.

VirtualBox has DHCP server which starts assigning IP adresses from 192.168.99.100.

1. Stop all VMs
   docker-machine stop ${docker-machine ls -q}
   This step will release all assigned addresses to VirtualBox DHCP
2. Start VMs in order
   docker-machine start vbox1 && docker-machine start vbox2 && docker-machine start vbox3
   This steps assign IP like this:
   192.168.99.100 : vbox1
   192.168.99.101 : vbox2
   192.168.99.102 : vbox3

Notice that docker-machine start vbox1 vbox2 vbox3 will not work, but I don't figure out why.

It's very useful.

[fernaspiazu]

In order to assign a static ip address 192.168.99.50 to my docker-machine (default) on VirtualBox, I used:

$ echo -e "kill \`cat /var/run/udhcpc.eth1.pid\`\nifconfig eth1 192.168.99.50 netmask 255.255.255.0 broadcast 192.168.99.255 up" | docker-machine ssh default sudo tee /var/lib/boot2docker/bootsync.sh > /dev/null

$ docker-machine restart default
Restarting "default"...
(default) Check network to re-create if needed...
(default) Waiting for an IP...
Waiting for SSH to be available...
Detecting the provisioner...
Restarted machines may have new IP addresses. You may need to re-run the `docker-machine env` command.

$ docker-machine env
Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.50:2376": x509: certificate is valid for 192.168.99.103, not 192.168.99.50
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.

$ docker-machine regenerate-certs default
Regenerate TLS machine certs?  Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Waiting for SSH to be available...
Detecting the provisioner...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...

$ docker-machine env
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://192.168.99.50:2376"
export DOCKER_CERT_PATH="/Users/mandrake/.docker/machine/machines/default"
export DOCKER_MACHINE_NAME="default"
# Run this command to configure your shell:
# eval $(docker-machine env)

My environment is OSX, VirtualBox (boot2docker.iso)

Hoping this can be useful 🙂
BTW: +1 for the new feature request 😉
Cheers.

[karaoguz-els]

Yes, there is an option to create with specific ip. All you need to do is specify ip/ip-range with
--virtualbox-hostonly-cidr option.

For example:

• when you want to assign specific ip, let say you want to assign 10.15.1.24, then appropriate config will be (the most important thing is the mask that we are using here. For specific ip you need to set subnet mask to 32) :
  docker-machine create --driver virtualbox --virtualbox-hostonly-cidr "10.15.1.24/32" dev

• if you want to pick an ip from specific ip range, then you need to use appropriate subnet mask.

[jandetlefsen]

If you issue is that you have to keep updating your host file you can just install Avahi on your container and use mDSN.

[mbishr]

It will be very useful to activate this feature to able to assign static ip address while creating vm using docker-machine