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.

How do you handle backups? Install restic or whatever in every container and set it up? What about updates for the OS and docker images, watchtower on them I imagine?

It sounds like a ton of admin overhead for no real benefit to me.

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

Regardless of VM or LXC, I would only install docker once. There’s generally no need to create multiple docker VMs/LXCs on the same host. Unless you have a specific reason; like isolating outside traffic by creating a docker setup for only public services.

Backups are the same with VM or LXC on Proxmox.

The main advantages of LXC that I can think of:

• Slightly less resource overhead, but not much (debian minimal or alpine VM is pretty lightweight already).
• Ability to pass-through directories from the host.
• Ability to pass-through hardware acceleration from a GPU, without passing through the entire GPU.
• Ability to change CPU cores or RAM while it’s running.

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

Ahh gotcha, selective sync or virtual file system are the common terms for that. Nextcloud supports it, Owncloud does too and I think Owncloud Infinite Scale does but it’s not 100% clear.

When you say Owncloud couldn’t keep files local without uploading, was that with VFS enabled on the client?

Syncthing works great, if you want a web based file browser you can install one of the many available on a server with syncthing.

Longest interval is every 24 hours. With some more frequent like every 6 hours or so, like the ones for my game servers.

I have multiple backups (3-2-1 rule), 1 is just important stuff as a file backup, the other is a full bootable system image of everything.

With proper backup software incremental backups don’t use any more space unless files are changed, so no real downside to more frequent backups.

USB hard drive? If we’re talking about a cold backup that’s easy to access a USB drive is reliable and easy.

Yeah pinning is great, you’ll still need watchtower for auto updates too

Komodo is a full management setup, similar to Portainer, Dockge, etc… It works reasonably well.

Watchtower doesn’t require any labeling unless you want to exclude a container.

but my main concern is having a breaking change be automatically updated

Pinning to a major version usually solves this, ie; instead of using postgres:latest use postgres:14 which will give you updates only from version 14.

But also have backups in place, worst case you just roll back to before it updated.

Maybe Karadav with the Nextcloud clients/apps.

Not sure if that will support selective sync, I don’t see anything saying specifically no on the repo.

Yeah give it a try, I use -75dBm as my setting. Currently only on the 5ghz band, but you can try on all of them, 2.4ghz might want more like -80dBm.

I run proxmox on the host with docker in a VM for 90% of my stuff, OS updates I do like every 6 months maybe, I’ve done 1 major version upgrade on proxmox with no issues at all.

The docker containers auto-update via Komodo, and nothing really ever breaks anymore other than the occasional container error that needs a simple fix.

Everything important is backed up nightly using both proxmox backup server, and to backblaze B2 with restic.

I’ve found that a lot of clients just don’t roam well, they hang on to even unusable weak signals.

On my Unifi setup I’ve ended up turning on minimum RSSI on the APs so they force kick off any devices with a signal that is too low. You end up with a delay of like 5-10 seconds while the client reconnects, but it does work.

You don’t need any guides for it except for really niche cases.

For example Ubuntu VM; click create VM, choose Linux for the type, click next a bunch and choose your ISO image, CPU cores, and RAM. And you’re done, there’s no specific settings to use.