In what way is it not working?
I suppose you could create a stub zone in unbound with the NS record set to the home DNS server. As long as routing is working correctly, you shouldn’t need to specify an interface.
If that doesn’t work, maybe try a different DNS server with more powerful configuration.
No, I recommended Docker in a VM.
I don’t think Proxmox LXC containers support Docker well, if at all, so no.
I have one VM for running Docker stuff (i.e. the arr stack, jellyfin, etc.). Unless your hypervisor supports docker containers natively, separating them is just going to make it more difficult for you for no good reason.
I don’t run anything else in Docker right now, but if I did, I’d probably stick it in the same VM for now to save on overhead. If it was enough to be its own stack, I’d separate it.
Seems like a bug in the app. I’d open an issue on the project.
Considering you can assign any IME to any file, that means technically it supports everything from plain text to proprietary binary data.
ClamAV is great for exactly one thing: checking the “has antivirus” checkbox on company security audits.
Don’t get me wrong, it’s a real AV product, but there’s no real need for it. You’ll get much better results just being careful about what you run and having a system and network firewall. And not running everything as root.
The explanation is that it’s random. Generate enough random strings and you’re bound to get everything.
It’s not needed because it’s currently mostly working for them? You’re going to need to use full sentences if you want to communicate, I’m afraid.
They already have several VMs, containers, and want a full desktop on one. If it sounded like going down to one physical server would be appropriate, I would have recommended it. But condensing whatever they’ve got now would be a huge pain, especially if they find out it doesn’t work and they have to start over and go back to VMs and containers.
Why what?
You want KVM.
But I’d check the performance on the NAS first. They’re not really built for VMs so you might be missing hardware features, but I’d check resource usage to see if you’re maxing anything out. And try reducing resolution, color depth, etc. to make it easier.
Proxmox is just Debian. Use any partition-aware copy tool. If you have it set up for UEFI, just copy the EFI partition and all that stuff too and you should be set.
First, don’t use .local, as it’s used by mDNS. You should use .internal or a domain you own. I recommend changing before you get any more committed to your environment.
I’m not really following your post, because you’re not specifying whether each point is on the server or laptop.
Personally, I dislike Ubuntu on the server because of how it runs stuff like systemd-resolvd, which as you’ve experienced, gets in the way of standard operation.
If instances are unmaintained, losing them is probably a good thing.
Lemmy should do something like make captcha and email verification the default in the next version, and reject federation from anyone with a lower version. If we accept federation from any instance where this was never turned on, banning accounts one by one is worse than Sisyphean. They’ll just keep finding more vulnerable instances that are already trusted and abuse them to spam the rest of the fediverse.
If admins want to manually turn it off, then they should be prepared to manage that.
Does the error have any text that might be helpful?
Easier? Yes, definitely. Maybe work on the Vaultwarden stuff in parts, instead of all in one go.
Also, if you’re using Proxmox, you might just back up your whole VM to PBS. That’s how I do it. But that takes a bit of work to set up on its own.
It doesn’t need to exist at all. But being online and continuous obviously speeds communication.
Is this a response to my question or suggestions, or are you just restating your original post? I understood your scenario just fine.