A simple /etc/hosts file injection tool to resolve names of local Moby containers on the host. It uses the Moby Engine API and remains compatible with Docker Engine. It is inspired by docker-hoster by David Darias.

The container image is available on Docker Hub. A sample compose.yaml file is provided in the repository.

By default, the Moby client connects to /var/run/docker.sock. A different Moby-compatible API endpoint can be selected with the standard DOCKER_HOST, DOCKER_TLS_VERIFY, and DOCKER_CERT_PATH environment variables.

Container hoster is configured via environment variables. If no env variable is set, container-hoster will use the default value. The following variables are available:

• CH_HOSTSFILE: The path to the hosts file to be injected. Defaults to /hosts. The real hostsfile should be mounted as a bind mount to this path.

• CH_INTERVAL: The interval in seconds to check if an update for the hostsfile is needed. It is formatted as a Go duration string. A duration string is a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms", "-1.5h" or "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". Defaults to 10s.

• CH_HOSTNAME_FROM_CONTAINERNAME: If set to true, the container name will be used as the hostname. Defaults to true.

• CH_HOSTNAME_FROM_LABEL: If set to true, the value given in container label de.wollomatic.container-hoster.name will be used as hostname. Defaults to false.

• CH_ONLY_LABELED_CONTAINERS: If set to true, only containers with the label de.wollomatic.container-hoster.enabled=true will be added to the hosts file, and all other containers are ignored. Defaults to false, so every container is added to the hosts file.

• CH_NETWORK_REGEXP: A regular expression to match the network name of the container. Only containers with a matching network name will be added to the hosts file. Defaults to .*.

• CH_LOG_EVENTS: If set to true, all docker events which lead to rewriting the hosts file will be logged to stdout. Defaults to false.

Container labels are optional. The following labels are available:

• de.wollomatic.container-hoster.name: The hostname to be used for the container if CH_HOSTNAME_FROM_LABEL is set to true.

• de.wollomatic.container-hoster.enabled: If set to true, the container will be added to the hosts file.

• de.wollomatic.container-hoster.exclude: If set to true, the container will be excluded from the hosts file.

In most cases, the container-hoster container will be run as root. This is necessary to write to the hosts file and connect to the Moby API socket. Giving a container access to the API socket is potentially dangerous because that access can usually control the engine. Container-hoster only lists containers and listens to engine events; it does not start or stop containers. It updates the hosts file when relevant container events occur.

The runtime container image is made from scratch and contains no additional software beyond the application and its Moby client (ex. Docker SDK) dependencies.

Container-hoster does not need to have access to any network.

• 0.1.x: Renaming containers will now update the hosts file.

This project is licensed under the MIT license

• see the LICENSE file for details

Thanks to David Darias for the original idea docker-hoster.