docker-etchosts

Automatically manages entries in hosts file (/etc/hosts) for local docker containers.

Its main use-case is working on multiple web-accessible projects without having to keep track of different exported ports, instead relying on predictable names.

Inspired by vagrant-hostmanager and docker-hostmanager.

Installation

To install from source, dep must be used:

go get -d github.com/costela/docker-etchosts
cd $GOPATH/src/github.com/costela/docker-etchosts
dep ensure -vendor-only
go install

And run it as docker-etchosts

Alternatively, it's also possible to run docker-etchost from inside a docker container itself, giving it access to both the hosts file and the docker daemon:

docker run -d \
  --network none --restart always \
  -v /etc/hosts:/etc/hosts -v /var/run/docker.sock:/var/run/docker.sock \
  costela/docker-etchosts

Usage

Once started, docker-etchosts creates /etc/hosts entries for all existing containers with accessible networks. It also listens for events from the docker deamon, updating the hosts file for each container created or destroyed.

Entries are created for each container network with the following names:

• container name plus all network-specific aliases
• (optionally) each of the above with the docker-compose project name appended
• each of the above with the network name appended (except for the default bridge network)

Each container will thereforr have up to 4 entries per alias: CONTAINER_ALIAS, CONTAINER_ALIAS.PROJECT, CONTAINER_ALIAS.NETWORK_NAME, CONTAINER_ALIAS.PROJECT.NETWORK_NAME

This means the following docker-compose.yml setup for project someproject:

services:
  someservice:
    ...
    networks:
      somenet:
        aliases:
          - somealias

Would generate the following hosts entry:

x.x.x.x     someservice someservice.somenet someservice.someproject someservice.someproject.somenet somealias somealias.somenet somealias.someproject somealias.someproject.somenet

NOTE: Docker ensures the uniqueness of containers' IP addresses and names, but does not ensure uniqueness for aliases. This may lead to multiple entries having the same name, especially for the shorter name versions. The longer, more explict, names are there to help in these cases, enabling different workflows with multiple projects.

To avoid overwriting unrelated entries, docker-etchosts will not touch entries not managed by itself. If you already manually created hosts entries for IPs used by containers, you should remove them so that docker-etchosts can take over management.

All entries managed by docker-etchosts will be removed upon termination, returning the hosts file to its initial state.

Configuration

docker-etchosts can be configured with the following environment variables:

• ETCHOSTS_LOG_LEVEL: set the verbosity of log messages (default: warn, possible values: debug info warn error)

• ETCHOSTS_ETC_HOSTS_PATH: path to hosts file (default /etc/hosts)