Besides lots of other cool stuff it can do (including monitoring for a lot of your self hosted stuff), HomeAssistsnt has the Feedreader integration, which lets you poll RSS feeds. You can then create automations to send notifications to you through the HomeAssistsnt companion app.
Feedreader defaults to polling once per hour, but you can change this in the configuration.
Are you running docker on the PVE host? Or within a LXC container or VM?
Note that running docker on the PVE host is not recommended as this can cause networking problems for both docker and the host+guests
If you are running docker in a VM as is recommended then pass thru the USB drive to that VM, it will act as if it was plugged directly into the VM.
Proxmox is great but if you are happy on unraid then it does make a lot of things simple that may or may not (depending on what we’re talking about) be as easy on PVE. For example, PVE is not a storage solution first; sure you can do lots of storage stuff but you should not host shares directly off it for example (set up a container or VM to host the shares passed through from the storage pool on the host box).
You get more control and customization (which is where I was very happy; I have a cluster and my network shares are a service I manage within that) but if you are looking for a NAS-first solution for a single server, give something like TrueNAS Scale a good look before you take the plunge.
It’s probably not blocking DNS-over-HTTPS
It is, in fact, the only Snap I’ve ever used which worked without issues
That being said, it’s kinda slow in some cases, but perfectly useable nonetheless
Looks like I’ve got a project for next weekend
If an attacker wants your encrypted data that bad, they will attack the running machine and use it to access the data, they will not steal a key and then attempt to physically remove the drive.
Drive encryption is for prevention of access when the drive is offline, it doesn’t protect a running system which can access that data.
If you are worried about the key being accessed while the machine is running, focus on hardening access to the machine via network, etc.
IPv6 typically assigns blocks to endpoints, not single WAN IPs (ie there is no NAT).
Changing this often would be absolute chaos for all connected devices, even if they’re configured correctly.
Be aware that, in the past anyway, Docker didn’t like some storage mediums when running in LXC (I think there are [were?] issues if you snapshot the LXC image on ZFS and you’re using the Overlay2 driver for Docker), and that you could often find issues with networking that way as well (might be a problem if you are trying to cluster/swarm between multiple LXCs?). For those reasons I’ve kept all my Docker stuff in kvm rather than LXC, I wasn’t experienced enough to untangle it all.
Fucking up in EZ mode just becomes an hour wasted.
Having full backups is good too, of course.
Why the downvote for Guacamole? Is it because it’s not practical to OPs question? Did something happen with the project? I’m not up to speed, but have been mulling over using it for my setup for a while now.
It would help to be explicit yeah. If only for the reason that sometimes your issue could be caused by the way you set things up.
For reference, I have some LXCs with docker as an experiment( a privileged container with nesting=1 (also fuse=1 and keyctl=1, not sure if those help) and I haven’t had problems, but they’ve never needed a restore. I think unprivileged is where you will run into problems.
For doing what you want, you’ll want to bind mount your external drive. I’d recommend not using drive letter mounts (“/dev/sdc” for example) as those can change across reboots. Instead, use /dev/disk/by-id/<find-your-disks-id-and-put-it-here> which is the same no matter when the disk is mounted on the host. To make a bind mount, you have to edit the .conf file for your container on the host at /etc/pve/lxc/<vmid>.conf where the <vmid> is the container is number and then start the container back up. The disk will then appear in the container mounted at the path you specify. Check out the Proxmox docs for LXC bind mounts for info on how to configure that.