![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
This guy gets it.
This guy gets it.
This app got me laid,” says one five-star review on the Apple App Store. “Best way to buy tickets for events. 2nite is the truth and the future,” the horny user wrote.
This author knows what’s up. Most glorious ending to a news article I seen in a while.
> mfw the paywall is preventing me from reading his “story” more than the Biden administration 🙄🥱😂
Star Wars: X-wing vs TIE Fighter
https://en.m.wikipedia.org/wiki/Star_Wars:_X-Wing_vs._TIE_Fighter
Steam is your best bet here. I’ve been playing Baldur’s Gate. Previously played Civ VI a lot… lots of great choices.
I’d recommend checking out Linux Mint with the “cinnamon” desktop.
Installing hardware drivers and software is a breeze. It comes with a software manager for easily adding new programs.
Screenshot included for convenience:
Are AI products released by a company liable for slander? 🤷🏻
I predict we will find out in the next few years.
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:{ "dns": ["<Pi-hole IP>"] }
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
Check Firewall Rules: Ensure there are no firewall rules on your host or network equipment that might be blocking traffic from the new networks.
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.
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.