Issue Type: | New Feature |
---|---|
Priority: | 4 - Normal |
Status: | Resolved |
Created at: | 2015-04-02T20:46:31.000Z |
Updated at: | 2018-05-07T17:50:30.894Z |
Created by: | Michael Zeller |
---|---|
Reported by: | Michael Zeller |
Assigned to: | Josh Wilsdon |
Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2015-04-16T06:00:18.000Z)
2015-04-16 Mars Climate Orbiter (Release Date: 2015-04-16)
Customers have asked that we support dockers dns flags
ravio:~ Michael.Zeller$ docker help run | grep dns --dns=[] Set custom DNS servers --dns-search=[] Set custom DNS search domains (Use --dns-search=. if you don't wish to set the search domain)
Their use case involves a dns service that auto registers services and search domains for different environments(dev/prod).
I mentioned on docker@ that currently we set dns based on the values from the networks chosen for the provision.
@accountid:557058:a348ec04-3066-457c-8197-c6cfc6e56d48 seemed ok with the plan that we would ignore any values from the network if a user specifies these options and use these specified values instead.
From @accountid:6245dc81699649006ae71bff on why he thinks this is essential to prioritize:
Moving the burden of DNS configuration to inside the container breaks with how things are conventionally done in Docker right now. This is bad for developer workflows. If I have to setup DNS in sdc-docker but not in lxc-docker it breaks the notion of portability.
Docker is working on making /etc/hosts and /etc/resolv.conf writable, but I don't believe that work has been release yet. Rather, everyone has been advised that configuring DNS on docker run is the best way to go about it.
Moreover, if we don't had this feature than it increases the time it takes for developers to deploy a given docker image because you no longer can deploy just the vanilla image, rather you extend the image and add in the DNS config there.
sdc-docker commit f45bf34 (branch master, by Josh Wilsdon)
DOCKER-308 add support for --dns and --dns-search