Add docker DNS resolver configuration option about awx HOT 2 OPEN

@jacobmaussocc

Thank you for your feedback.

Can you provide the details of your host?
Some distros provide intermediate dns cachers, which give rise to problematic behaviours. (systemd-resolved/...). You might see that your /etc/resolve conf points to 127.0.0.1 which is an intermediate caching and resolver.

The reason I ask this is that per the docker documentation, docker is configured to use host DNS.
https://docs.docker.com/network/

There are any number of configuration scenarios and intermediate DNS cachers that could provide an undesired experience like the one you are describing.

In some cases system administrators turn off these local daemons and just maintain /etc/resolve with the appropriate upstream DNS servers.

I'm not suggesting you do this, but if you can provide a better understanding of your configuration, we might be able to provide better guidance with your particular setup.

docker-compose absolutely does provide for the type of request you are suggesting, that may very well be a good enhancement for AWX/tower/AAP.

If look forward to understanding this issue further.

from awx.

@jacobmaussocc @dmzoneill the docker-compose env is for development purposes only. If you are hitting this issue because you are trying to develop a feature for AWX, we are definitely happy to help debug that but the docker-compose environment is not built to persist. If this instance needs to persist, I would suggest installing via the operator.

from awx.