Don’t threaten me with a good time!

“Hahahaha, I’ll GET HIM and steal his moment by quitting and losing on purpose!”, said no one ever.

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:

   docker network inspect old_main
   docker network inspect cloudflared
   

   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:

   {
     "dns": ["<Pi-hole IP>"]
   }
   

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:

   version: '3.7'
   services:
     cloudflared:
       image: cloudflare/cloudflared
       networks:
         - cloudflared
   
   networks:
     cloudflared:
       external: true
   

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:

   docker run --rm -it --network cloudflared alpine ping -c 4 google.com
   

   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:

   docker network rm cloudflared
   docker network create cloudflared
   

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.

Star Wars: X-wing vs TIE Fighter

https://en.m.wikipedia.org/wiki/Star_Wars:_X-Wing_vs._TIE_Fighter

I’ve thought about that before. 😂

In all honesty, $TSLA made a lot of people rich 3 to 4 years ago. I’m not the only one.

I honestly don’t care which companies do it, but I’ve always been interested in green investing. When so many governments are pouring money into energy transition, there’s bound to be profit to be made.

I sunk about 70k into $TSLA in 2020. Sold the brokerage shares to pay off my mortgage and buy a Model X for my family. The stock also grew my kids’ UTMA accounts to pay for about half of college, or perhaps large down payment on their future home.

There were a lot Tesla of haters back in 2020. There are probably more now. But whatever your opinion may be, that company has changed the world for the better. Accelerated the transition to electric transport: just like they said they’d do. I’m excited for the second generation to succeed: Rivian, BYD, and other companies who’re serious about it.

Best financial move I ever made? Latch on to a company that has purpose and a great product, then cash out for the things that matter. I just wish I’d had capital back when Apple launched the iPhone!

(P.S. to all the haters who’re gonna come at me with downvotes: I have more dollars than the number of downvotes you’ll ever be able to dish out! So come at me brah.)