It sounds like your issue might be related to how your Docker networks are configured for DNS and internet access. Try these:
**Check Network Configuration:**Ensure your new networks are correctly configured to allow internet access. Docker networks should be able to route traffic to the internet by default unless specified otherwise.
**DNS Configuration:**Since you’re using Pi-hole for DNS, make sure the new networks are properly configured to use Pi-hole as their DNS server.
**Inspect Network Settings:**Compare the settings of old_main with the new networks. Use the following command to inspect the network configuration:
Pay attention to the gateway, subnet, and any custom DNS settings.
**Check Docker Daemon Configuration:**Verify that your daemon.json file is correctly set up to use Pi-hole for DNS. It should look something like this:
**Verify Container Configuration:**Ensure that your containers are correctly configured to use the new network. This can be specified in your docker-compose files like this:
If this fails, the issue is likely with network configuration rather than the containers themselves.
**Docker Network Restart:**Sometimes, Docker networks need to be restarted to apply changes correctly. Try removing and recreating the problematic networks:
If none of the above steps resolve the issue, there might be a deeper configuration problem. At this point, it might be helpful to see the exact configuration of your docker-compose files and the output of the network inspection commands.