qx128

TL:DW…

Money.

I chuckled at the part at the end, that basically says “some people voiced concerns over switching to an open source solution because of support and SLAs”. It’s like, “yoooo, you just got fucked, in a concerted effort by a large company to shed customers that ‘don’t matter’ to them. What makes you think an open source could be worse than this?”

Lies. This is clearly a photo of Baldur’s Gate. 🙄

I see two basic reasons.

1. it gives companies plausible argument to embed telemetry into their products. Should your TV manufacturer or coffee maker manufacturer be able to monitor every single button you press on your device? Probably not, but they would like to “because AI”! Now they have an excuse to be as invasive as they want, “to serve you better”. The dream - for them - would be total surveillance of your habits to sell you more shit. Remember, it always comes back to money.

2. The old adage never fails: if it’s free, you are the product. Imagine AI being so pervasive, that now everywhere you look, everything you interact with can subtly suggest things. It doesn’t have to be overt. But if AI can nudge the behavior of the masses to do a thing, like buy more soda, or favor one brand over another, then it has succeeded in boosting company bottom line. Sure the AI can do useful shit for you, but the true AI problem companies want to solve is “say or do the right shit to influence this consumer to buy my thing”. You are the target the AI is operating on. And with billions of interactions and tremendous training, it will find the optimal way to influence the masses to buy the thing.

Don’t threaten me with a good time!

Oof. Sadly, events of the last few years support your statement. 🙄

Turns out violent threats are not protected speech under the first amendment. Who knew?!

Fuck around and find out.

I can attest this is true for me. I was shopping for a new clothes washer, and was strongly considering an LG until I saw it had “AI wash”. I can see relevance for AI in some places, but washing clothes is NOT one of them. It gave me the feeling LG clothes washer division is full of shit.

Bought a SpeedQueen instead and been super happy with it. No AI bullshit anywhere in their product info.

“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.