I had the same issue with mine when the network team created new networks that conflicted. Even after having updated that file with the docker_compose_subnet, and re-ran the deployment, it still hadn’t updated it. Please make sure you take a VM snapshot or backup prior to running the below commands.
To resolve, you would need to do the following:
docker stop $(docker ps -aq) This will stop all your containers so we can update the networking
docker network ls Find the current awx network listed, and copy the associated network id. We are going to want to delete this network
docker network rm
docker network create --driver bridge --subnet ‘192.168.168.0/24’ --gateway ‘192.168.168.1’ awxcompose_default create new network. Match whatever network is configured as your docker_compose_subnet
Once you have re-run the deployment, it should see the awxcompose_default network configuration, and use the networking provided in that.