1
I use docker-compose to run a small harem of containers in support of an application. The use of Docker's internal DNS resolver (e.g. db
resolves to the database backend container) is key to these. I use a private bridged network created with docker network
.
I am wondering if there is an easy and straightforward way, without the bureaucracy of Kubernetes and that, to take advantage of the DNS discovery mechanism while spreading the containers out onto multiple physical servers. One option is to simply build a separate Docker installation and private network network on another server and have these containers update DNS entries for themselves in my PowerDNS server upon startup, and there is an existing mechanism for that. However, I greatly prefer to leverage Docker's internal DNS discovery.
Any pointers would be appreciated!