qx128 , 1 month ago

It sounds like your issue might be related to how your Docker networks are configured for DNS and internet access. Try these:

1. **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.

2. **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.

3. **Inspect Network Settings:**Compare the settings of old_main with the new networks. Use the following command to inspect the network configuration:

   
   <span style="color:#323232;">docker network inspect old_main
   </span><span style="color:#323232;">docker network inspect cloudflared
   </span>
   

   Pay attention to the gateway, subnet, and any custom DNS settings.

4. **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:

   
   <span style="color:#323232;">{
   </span><span style="color:#323232;">  </span><span style="font-weight:bold;color:#183691;">"dns"</span><span style="color:#323232;">: ["<Pi-hole IP>"]
   </span><span style="color:#323232;">}
   </span>
   

5. **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:

   
   <span style="color:#63a35c;">version</span><span style="color:#323232;">: </span><span style="color:#183691;">'3.7'
   </span><span style="color:#63a35c;">services</span><span style="color:#323232;">:
   </span><span style="color:#323232;">  </span><span style="color:#63a35c;">cloudflared</span><span style="color:#323232;">:
   </span><span style="color:#323232;">    </span><span style="color:#63a35c;">image</span><span style="color:#323232;">: </span><span style="color:#183691;">cloudflare/cloudflared
   </span><span style="color:#323232;">    </span><span style="color:#63a35c;">networks</span><span style="color:#323232;">:
   </span><span style="color:#323232;">      - </span><span style="color:#183691;">cloudflared
   </span><span style="color:#323232;">
   </span><span style="color:#63a35c;">networks</span><span style="color:#323232;">:
   </span><span style="color:#323232;">  </span><span style="color:#63a35c;">cloudflared</span><span style="color:#323232;">:
   </span><span style="color:#323232;">    </span><span style="color:#63a35c;">external</span><span style="color:#323232;">: </span><span style="color:#0086b3;">true
   </span>
   

6. **Check Firewall Rules:**Ensure there are no firewall rules on your host or network equipment that might be blocking traffic from the new networks.

7. **Test Connectivity:**Run a simple connectivity test from within a container on the new network to check internet access:

   
   <span style="color:#323232;">docker run --rm -it --network cloudflared alpine ping -c 4 google.com
   </span>
   

   If this fails, the issue is likely with network configuration rather than the containers themselves.

8. **Docker Network Restart:**Sometimes, Docker networks need to be restarted to apply changes correctly. Try removing and recreating the problematic networks:

   
   <span style="color:#323232;">docker network rm cloudflared
   </span><span style="color:#323232;">docker network create cloudflared
   </span>
   

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.