I moved from pihole to technitium roughly two years ago. I was tired of pihole not doing “adult” DNS things, like zone transfers. Technitium is a real DNS server, pihole is just a resolver. You can create actual soa and srv records with technitium.

It already could sync zones, I’ve been doing primary -> secondary zone transfers for at least two years.

It didn’t sync lists and other configs, though. That’s new.

Edit: sorry, I misread the question. I haven’t run into any docker containers that don’t run on incus, but my testing is limited.

Well, I have run the homeassistant core docker, calibre web automated, and a bunch more.

One just needs to add the docker https path to its repository and the rest is just translating the options to the way incus starts these. (Sorry, I can’t exactly remember what incus uses to run these containers.)

Anyway, I can dig up some helpful documentation if you’re rally interested.

I moved to incus from proxmox nearly 18 months ago and I haven’t looked back.

Yes, sorry. I meant incus, not incus os.

IncusOS supports OCI containers, which means it can run most docker containers natively. And LXC, and vms via QEMU/KVM.

Oh, OK! Brilliant, I will check on this and report back.

Tempus is great, good job.

Very nice.

I’m afraid to ask, but I can’t seem to figure out how to add an http stream to the radio section… Is this feature active?

Don’t trust the TV, put Snort or suricata on that in passive bridge mode. Heck, even TCP-dump should see some activity when you turn on the TV.

Go look at the code in github. It’s one person, and it’s just bash scripts.

Yes, but you were casting compromise as a choice between giving your CC info and your ID, and making it look like these are all inevitable to the end user.

Let’s not forget that Google is the bad guy enacting these rules, and for Pete’s sake, stop blaming the user.