Replica deployment fails when "dns" is used.

[rjeffman]

When creating a deployment with a custom container file and using the dns option, the ipareplica role fails with:

TASK [ipaclient : Install - IPA client test] ********************************************************************************
fatal: [replica]: FAILED! => {"changed": false, "msg": "Failed to verify that m1.ipa.test is an IPA Server."}

Servers and clients are correctly deployed, even if multiple deployments are used on the same configuration.

[rjeffman]

As of the current version, this issue is still valid, although the effect is that the replica is partially deployed, and fails during first replication.

[rjeffman]

To circunvent this issue, use container_fqdn: true (See #3).

[rjeffman]

The docker compose spec does not define dns or disable-dns for networks, instead in forces the use of external networks.

This behavior is implemented in ipalab-config, but as the goal is to have the whole configuration in a single file, this issue will be kept open until there's a better solution or containers/podman-compose#1104 gets merged and released.