namefoki.blogg.se

1. #Adguard home docker install
2. #Adguard home docker update
3. #Adguard home docker software
4. #Adguard home docker code

Using Ansible to setup the underlying “bare metal” hardware.Using Docker-Compose to maintain distinct services.With that, here’s how I re-over-engineered my home network with a few improvements to how I setup, maintain, and manage things: To head down this route, beyond having read the original post along with some basic familiarity with home networking (understanding how things like DNS and IPs work), it would help to have some conceptual familiarity with containerization and provisioning tools to adapt the setup to your own needs.

#Adguard home docker update

Ideally, systems would update themselves regularly, and upgrades would be predictable and boring. I wanted to get out of the bespoke sysadmin business, provisioning and then immediately walking away from “set it and forget it” systems wherever possible.

#Adguard home docker code

While config as code may come more naturally when managing a cluster of servers, even when managing only a single Raspberry Pi, prefer defined and well-understood changes over guess-and-check server administration. Config (and infrastructure) as code - This is by far from a new concept to the industry, but I was somewhat-recently introduced to the idea of treating servers like cattle, not pets.

#Adguard home docker software

What I wrote then remains true, but after having relied on, optimized, and upgraded what I described in my previous post for about eighteen months now, I’ve decided to build on what’s there by revisiting re-over-engineering how I setup, maintain, and manage the software and services that power and protected the network with a number of specific goals in mind: If you haven’t already checked that post out, it walks through how I used a UniFi Dream Machine (although most routers would work), a Pi-Hole to block ads and tracking, cloudflared for DNS over HTTPS, and Cloudflare Gateway to block malware/phishing to (over) optimize my home network for privacy and security. Image: lucaslorentz/caddy-docker-proxy:ci-alpineĬaddy_0.reverse_proxy: :3000Ĭaddy_1.reverse_proxy: little less than a year ago, I wrote a now-popular post about how I over-engineered my home network for privacy and security. Got it working like this, proxying 2 containers that run in host network mode: version: "2.4" Is there a way for Caddy-Docker-Proxy to proxy local stuff that is not in its network? It doesn’t even need to know anything about the AdGuard container. This is necessary for AdGuard to function properly (without forcing me to create multiple macvlans). Correct, my Compose file shows AdGuard is using network_mode: host. I will likely forget I ever modified that file.Ĭaddy-Docker-Proxy gives an error about AdGuard, it cannot proxy adguard.o because that container is not in the same docker network. However, I would like to manage everything with Caddy and not mess with system files. curl Ĭurl: (6) Could not resolve host: docker.oĪgain, it is no issue on other devices within my LAN (or even if I VPN into my LAN, the domain works).Īdding 192.168.88.2 docker.o to my /etc/hosts file on my server DOES allow me to access Portainer via that url on my server. I made sure this is not related to the browser that I use. Is there a way for me to configure caddy-docker-proxy in such a way that the local domain will also work on the server itself? 4. I often use my server as my desktop workstation and like to use the domain, just like I use it on my phone, laptop when I am at home. On the server I can still access Portainer via localhost:9000 and 192.168.88.2:9000 but not via. Problem: on my server itself, gives a page not found. However this only works on other devices such as my laptop or my phone. Fantastic! No need for me to type IP addresses and portnumbers Now I can access Portainer via because Caddy-Docker-Proxy is Proxying the docker.o to the Portainer container. In AdGuard Home, I have also set a few DNS rewrites such as: 192.168.88.2 docker.o

In my router, the only DNS provider is the IP address of my server (192.168.88.2 that runs Docker Compose. I use AdGuard Home as my LAN’s DNS provider. var/run/docker.sock:/var/run/docker.sockĬaddy.reverse_proxy: "" Service/unit/compose file: version: "2.4"

#Adguard home docker install

Manjaro Gnome clean install with docker compose b.