Add /etc/hosts entry for docker machine

[RaasAhsan]

When a docker machine is brought up, is there any way to automatically add in a /etc/hosts entry for the IP of that machine? I want some common keyword I can connect my services to rather than an IP. I can do this manually but it would be a neat feature.

[zakuni]

+1

[nathanleclaire]

I think this is a bit out of scope for machine CLI, but it makes me want a plugin model which could accommodate this, e.g. git hook style.

[josephabrahams]

+1

[FugDev]

+1

[bryannaegele]

So I noticed the Parallels provider does this by default, but not Virtualbox. When I create a machine with the Parallels driver it adds an entry like so:

xx.xxx.xxx.xxx  <machine-name>.shared <machine-name> #prl_hostonly shared

This is extremely convenient for the less technical people by automating this step.

I also found that it gradually increments the vm's IP with Parallels, but Virtualbox appears to always grab the lowest available IP in the pool. So if you had a machine on 192.168.99.100, stop it, then create another new box, the new box will be on 192.168.99.100 rather than .101.

So it seems this is more driver related than docker-machine related.

[the-destro]

this would also be advantageous for other tools, like docker-py, that are trying to assert the TLS hostname.

[BlueHotDog]

+1

[hassek]

+1

[gcuisinier]

+1, but the hook way seems more interesting

[anentropic]

+1 or even just a way to control which IP it chooses to use when starting a specific machine (preferably a stable IP per-machine) ...then I could at least hand edit my /etc/hosts file once and be done

[gcuisinier]

Specify an IP is not always possible. For example, in the case of Amazon, the IP is different each time you start an instance. This is the same for GCE I think, an probably for all cloud provider. To be complete, Amazon and GCE have the notion of eternal IP to keep it at each restart of the instance, but it is more expensive, and you cannot choose the IP anymore (the IP is provided by the cloud provided, in a certain range).

The addition of an entry in a the /etc/hosts is a better solution because it is not bound to a particular driver, and therefore more interesting.

But, IMHO, a hook system is even better, because more flexible. You this, you can do a lot of think :

• Add an entry in hosts file
• OR, Register the machine resolution in a dynamic DNS, and so the resolution is not only bound to an unique machine
• Add the machine in a monitoring tools
• ...

What do you think ?

[anentropic]

hook system - great being able to specify a specific ip for virtualbox would be a handy quick hack though

[gcuisinier]

I am not sure that is a quicky hack. To force the IP, I think you have to disable the VBox DHCP server and provide an other one that provide your IP.

Or to run command inside the VM to configure the network adapter (like Vagrant do I think).

[heycalmdown]

+1

[ghost]

+1 Trying to get TLS to cooperate with docker-py for automation tools would be way easier.

[Foo42]

+1

[jandre]

+1 would improve my automation immensely.

[dancompton]

+1

[sarink]

+1

[bamarni]

Had the same concern :+1:

At the moment I'm using a custom tool for this (https://github.com/bamarni/docker-machine-dns).

[mjumelet]

I created a simple script for which I added an alias in my ~/.profile (Tested only on OSX):

alias de=". ~/bin/de.sh"

https://gist.github.com/mjumelet/1cb8f0531243ee5733a6

Since it needs to modify /etc/hosts it will ask for your password

[iamKurt]

+1

[astewart-twist]

+1

[ernestm]

+1

[grisevg]

What about a simple sed replacement for the hosts file added to .bashrc?

[mateusz-lisik]

+1

[agusti-t]

+1

[charleskun]

+1

[BeaverCC]

+1

[apophizzz]

+1