ddh

He has angered the penguins

There are several ways around it. If you are self hosting for a small trusted group, or just yourself, you can use Tailscale.

You can install a Proxmox virtualisation cluster, a popular (the most popular?) option for self-hosting services. All nodes in the cluster are visible in a single web interface. For additional system coordination, you can set up High Availability and clustered file systems that the nodes can share.

Ooooo, a ruling

I reckon that mantle should go to Fedora Silverblue over Fedora Workstation.

The best posture is the next posture.

Sure, OpenWRT is good and there’s an Adguard Home plugin for it. You don’t need to buy any hardware to use Pihole though, many people run it in a container on an existing machine. So it comes down to the functionality you need or want and the software you prefer, right?

Use the second option of a static MAC to IP map and add the relevant records to each pihole’s local DNS.

Router may not have a function you want.

You can just run two DHCP servers. Give them non-overlapping ranges or give them the same MAC to IP mapping.

Kali, also called Kalika, is a major goddess in Hinduism, primarily associated with time, death and destruction.

All operating systems suck, some just suck harder than others.

Indeed it is difficult to hammer it in to shape. In addition, Microsoft will often quietly reset setting back in their favour. It’s that constant fight that tipped the scales for me.

My main issue with Windows isn’t its technology, but its attitude. The user is no longer the most important consideration. In that way it’s become adversarial.

On my kid’s laptop I was holding Windows 11 24H2 back because of Recall, but this week it just decided to install itself. Now it’s a Linux laptop.

After switching to Silverblue a couple years ago I’ve used dnf, like, three times maybe. I find rpm-ostree even simpler than apt since it’s easy to tell what additional packages I’ve installed, it’s trivial to remove them, and I’ve never had a dependency issue.

Basically, stay away from combustion exhaust. Of course there’s a scale: hydrogen = OK, wood = not good, burn pit = fucked up.

1. I’m backing up LXCs, like I’d back up a VM. I don’t back up Docker containers, just their config and volumes.
2. I don’t think anyone is doing that. We’re talking about installing Docker in LXC. One of the Proxmox rules you can live by is to not install software on the host. I don’t see the problem with installing Docker in an LXC for that reason.
3. I’ll snapshot an LXC before running things like a dist-upgrade, or testing something that might break things. It’s very easy, so why not?
4. I back up my LXC that has Docker installed because that way it’s easy to restore everything, including local volumes, to various points in time.

You can also create a single LXC for Docker and run multiple Docker containers on it. The VM argument is for security as it’s harder to escalate to the host from a VM than from an LXC.

If you do that, Docker is stuck on that host. If it’s in an LXC it can move to another host. Plus, backing up and snapshotting are easier IMO.