Go to file
mmmohebi 7ea0ee327b fix(hoster.py): Refactor event handling and hosts file update
Refactored the Docker event handling to use json parsing for more robust event processing. Updated the hosts file update logic to correctly handle existing sections and ensure atomic writes. Improved container info extraction and error handling.
2025-11-18 12:24:33 +03:30
.gitignore fix: Add hosts to .gitignore 2025-11-18 11:40:47 +03:30
Dockerfile Include support for docker network aliases 2018-06-30 16:38:01 -04:00
LICENSE Initial commit 2015-11-02 21:19:10 -05:00
README.md Update README.md 2018-07-01 13:31:51 -04:00
hoster.py fix(hoster.py): Refactor event handling and hosts file update 2025-11-18 12:24:33 +03:30

README.md

Hoster

A simple "etc/hosts" file injection tool to resolve names of local Docker containers on the host.

hoster is intended to run in a Docker container:

docker run -d \
    -v /var/run/docker.sock:/tmp/docker.sock \
    -v /etc/hosts:/tmp/hosts \
    dvdarias/docker-hoster

The docker.sock is mounted to allow hoster to listen for Docker events and automatically register containers IP.

Hoster inserts into the host's /etc/hosts file an entry per running container and keeps the file updated with any started/stoped container.

Container Registration

Hoster provides by default the entries <container name>, <hostname>, <container id> for each container and the aliases for each network. Containers are automatically registered when they start, and removed when they die.

For example, the following container would be available via DNS as myname, myhostname, et54rfgt567 and myserver.com:

docker run -d \
    --name myname \
    --hostname myhostname \
    --network somenetwork --network-alias "myserver.com" \
    mycontainer

If you need more features like systemd interation and dns forwarding please check resolvable

Any contribution is, of course, welcome. :)