You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.".
The text was updated successfully, but these errors were encountered:
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"
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."
.The text was updated successfully, but these errors were encountered: