![](/static/253f0d9b/assets/icons/icon-96x96.png)
Why not? You can just connect the PiHole container to both networks and inter-container communication should work as usual. I haven’t tried this with PiHole specifically but I’ve done it with other services in the past
Why not? You can just connect the PiHole container to both networks and inter-container communication should work as usual. I haven’t tried this with PiHole specifically but I’ve done it with other services in the past
Use gluetun, look up how to configure for your provider. Run a 2nd container for your torrent client, using network_mode: “service:gluetun”
to run all your traffic though the vpn. Note that if you’re forwarding ports from your client to e.g. access the web UI, you’ll need to forward them from the gluetun container instead.
You uh… you might have chosen the wrong field if you hate displacing labour
What exactly is Hyprland? I looked at the site quick but I couldn’t quite figure it out from the description.
Disclaimer: I’ve only ever used Linux servers, not really as a desktop beyond vanilla Ubuntu
How did you configure the rainbow text colors? I love the look (I’m on heimdall atm)
Funny, but feels unfair to mastodon (as someone who doesn’t use mastodon), they are definitely not trying to destroy the world and could use donations too!
Not for PiHole but I was testing this recently with traefik. This has a bunch of traefik stuff in there (I’m on mobile so it’s too hard to edit it) but hopefully you see how the networks work
# Testing macvlan setup for traefik # Will only work on linux because of macvlan network version: '3' services: traefik-whoami: image: traefik/whoami container_name: traefik_whoami networks: - bridge_network labels: - "traefik.enable=true" - "traefik.http.routers.whoami.rule=Host(`whoami.test`)" - "traefik.http.routers.whoami.entrypoints=http" traefik-reverse-proxy: image: traefik:v2.10 container_name: traefik_reverse_proxy command: - "--api.insecure=true" # Enable the API dashboard (insecure for testing) - "--providers.docker=true" # Enable Docker provider - "--providers.docker.exposedbydefault=false" # Disable exposing all containers by default - "--entrypoints.http.address=:80" # HTTP entrypoint - "--entrypoints.http.forwardedheaders.insecure=true" # Insecure forwarding (for testing) - "--providers.docker.network=bridge_network" # Use bridge network for traefik discovery ports: - "1180:80" # Expose HTTP entrypoint - "12345:8080" # Expose Traefik dashboard networks: bridge_network: {} macvlan_network: ipv4_address: 192.168.1.69 volumes: # TODO: Use docker.sock proxy instead of mounting directly # https://github.com/Tecnativa/docker-socket-proxy - /var/run/docker.sock:/var/run/docker.sock:ro labels: - "traefik.enable=true" - "traefik.http.routers.reverse-proxy.rule=Host(`traefik.test`)" - "traefik.http.routers.reverse-proxy.entrypoints=http" networks: bridge_network: driver: bridge macvlan_network: driver: macvlan driver_opts: parent: eth0 ipam: config: - subnet: 192.168.1.0/24 gateway: 192.168.1.1 ip_range: 192.168.1.69/32 # Must be outside router's DHCP range