Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 7. Networking

Troubleshoot networking issues.

7.1. Issue - The default subnet used in Ansible Automation Platform containers conflicts with the internal network

The default subnet used in Ansible Automation Platform containers conflicts with the internal network resulting in "No route to host" errors.

To resolve this issue, update the default classless inter-domain routing (CIDR) value so it does not conflict with the CIDR used by the default Podman networking plugin.

Procedure

  1. In all controller and hybrid nodes, run the following commands to create a file called custom.py: 

    # touch /etc/tower/conf.d/custom.py
    Copy to clipboard
    # chmod 640 /etc/tower/conf.d/custom.py
    Copy to clipboard
    # chown root:awx /etc/tower/conf.d/custom.py
    Copy to clipboard

  2. Add the following to the /etc/tower/conf.d/custom.py file: 

    DEFAULT_CONTAINER_RUN_OPTIONS = ['--network', 'slirp4netns:enable_ipv6=true,cidr=192.0.2.0/24']
    Copy to clipboard
    • 192.0.2.0/24 is the value for the new CIDR in this example.

  3. Stop and start the automation controller service in all controller and hybrid nodes: 

    # automation-controller-service stop
    Copy to clipboard
    # automation-controller-service start
    Copy to clipboard

    All containers will start on the new CIDR.

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat, Inc.