Crowdsec has default scenarios and lists that might block a lot of it, and you can pretty easily make a custom scenario to block IPs that cause large spikes of traffic to your applications if needed.

Basically everything. Self hosting doesn’t rely on public access.

Check the logs for the containers and see what the issue is first. Then go from there.

100% reliable so far, I’ve bought about 10 of them I think over the past 8 years or so. Some are in RAID 1 arrays, and some just on their own for backups and such.

The main thing is buy from a local shop or online place like serverpartdeals.com and not Amazon or other online marketplaces.

All my stuff is backed up several ways every night (which should be done no matter what drives are used) so it’s not that big of a deal if they failed suddenly.

Ease of use mostly, one click to restore everything including the OS is nice. Can also easily move them to other hosts for HA or maintenance.

Not everything runs in docker too, so it’s extra useful for those VMs.

A couple posts down explains it, docker completely steamrolls networking when you install it. https://forum.proxmox.com/threads/running-docker-on-the-proxmox-host-not-in-vm-ct.147580/

The other reason is if it’s on the host you can’t back it up using proxmox backup server with the rest of the VMs/CTs

Dockers ‘take-over-system’ style of network management will interfere with proxmox networking.