Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow configuration of network namespace container "extra_hosts" #6322

Open
djenriquez opened this issue Sep 13, 2019 · 2 comments
Open

Allow configuration of network namespace container "extra_hosts" #6322

djenriquez opened this issue Sep 13, 2019 · 2 comments

Comments

@djenriquez
Copy link

When using the pause container as the parent namespace container for tasks to join their network on, it becomes important to have the ability to control the /etc/hosts file so that services can continue to use a hostname as the connection string for their upstreams. This can be done by configuring "extra_hosts" for the docker driver, but we don't seem to have the ability to control the configuration of the pause container.

Since other tasks join the pause container's network, they are not allowed to use "extra_hosts" as they get the error "Conflicting options: custom host-to-IP mapping and the network mode.".

@tyler-domitrovich
Copy link

Similarly, it would be nice to have control over the /etc/resolve.conf file so that services may have control over the nameservers they evaluate. This can be done by configuring the "dns", "dns-opt", and "dns-search" options for the docker driver.

Since other tasks join the pause container's network, they are unable to use those options and receive the following error: "conflicting options: dns and the network mode"

@tgross
Copy link
Member

tgross commented Jun 16, 2021

#10766 will provide a better workaround for this issue but won't quite give full control, so I'm not going to close this issue out when that merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants