Oh, and we’re showing all your friends what you watch without you asking for it. And by friends, we mean everyone we leaked your account and payment details to. Twice.

Why the literal fuck anyone has anything to do with Plex at this point is beyond me. They don’t supply anything unique and they abuse you to do it.

Run a proxmox VM with docker services. ZFS snapshots and backups via PBS.

Debian. Just Debian. No drama.

I use Pinchflat, but I’ll take Youtube channel feeds instead so it can employ Sponsorblock and cut the commercials, especially for podcasters that use IHR. It then exports an RSS feed for Antennapod to monitor, but I imagine you could just write the episodes to a Navidrome-accessible folder.

Sounds like they give you a bunch of grafana dashboards preconfigured, which is fine. Makes customizing them easy.

deleted by creator

I’ve followed this project, and they’re very limited on the off-the-shelf mowers that are supported.

Frankly, I’d prefer a generic version that lets me slap some servos against the wheels on a basic cordless mower and drive it around with differential steering. I don’t need it to look pretty, I just want it to cut my grass.

So if I want a new container stack, I make a new Proxmox “disk” in the ZFS filesystem under the Hardware tab of the VM. This adds a “disk” to the VM when I reboot the VM (there are ways of refreshing the block devices online, but this is easier). I find the new block device and mount it in the VM at a subfolder of /stacks, which will be the new container stack location. I also add this mount point to fstab.

So now I have a mounted volume at /stacks/container-name. I put a docker-compose.yml in there and all data that the stack will use will be subfolders of that folder with bind mounts in the compose file. When I back up, that ZFS dataset that contains everything in that compose stack is snapshotted and backed up as a point-in-time. If that stack has a postgres database, it and all the data it references is internally consistent because it was snapshotted before backup. If I restore the entire folder from backup, it just thinks it had a power outage, replays it’s journals in the database, and all’s well.

So when you have a backup in PBS, from your Proxmox node you can access the backups via the filesystem browser on the left.

When you go to that backup, you can choose to do a File Restore instead of restoring the entire VM. Here I am walking the storage for my nextcloud data within the backups, and I can walk this storage for all discrete backups.

If I want to just restore a container, I will download that “partition” and transfer it to the docker VM. Down the container stack in question, blow out everything in that folder and then restore the contents of the download to the container folder. Start up the docker stack for that folder and it’s back to where it was. Alternatively, I could just restore individual files if I wanted.

Yes. So my debian docker host has some datasets attached:

mounted via fstab:

and I specify that path as the datadir for NCAIO:

Then when PBS calls a backup of that VM, all the datasets that Proxmox is managing for that backup take a snapshot, and that’s what’s backed up to PBS. Since it’s a snapshot, I can backup hourly if I want, and PBS dedups so the backups aren’t using a lot of space.

Other docker containers might have a mount that’s used as a bind mount inside the compose.yml to supply data storage.

Also, I have more than one backup job running on PBS so I have multiple backups, including on removable USB drives that I swap out (I restart the PBS server to change drives so it automounts the ZFS volumes on those removable drives and is ready for the next backup).

You could mount ZFS datasets you create in Proxmox as SMB shares in a sharing VM, and it would be handled the same.

As for documentation, I’ve never really seen any done this way but it seems to work. I’ve done restores of entire container stacks this way, as well as walked the backups to individually restore files from PBS.

If you try it and have any questions, ping me.

I wonder how they figure that’s going to work out.

I couldn’t imagine being this pants-shittingly stupid about how the internet works.

I run a docker host in Proxmox using ZFS datasets for the VM storage for things like my mailserver and NexcloudAIO. When I backup the docker VM, it snapshots the VM at a point in time, and backs up the snapshot to PBS. I’ve restored from that backup and it’s like the machine had just shut down as far as the data is concerned. It journals itself back to a consistent state and no data loss.

I wouldn’t run TrueNAS at all because I have no idea how that’s managing it’s storage and wouldn’t trust the result.

OK, does Ventoy now include tools of some sort and not just a way to boot ISOs? Because as far as I know, it just boots LiveUSB images you place on it. If one of those happens to have partitioning tools, you’re using the tools included in that distro.

I do this with a calibre/calibreweb docker stack, and fbreader on my tablet/phone. Unfortunately you need to use g drive for progress sync, but that’s not a huge roadblock.

Does it sync progress?

Finally got a drive to replace a deader in my zpool. Raid10 ftw

Montenegro has LARPing brownshirt cops too, eh?

deleted by creator

I’ve been using the same windows/dockur setup for a couple years that they outline in the Winapp docs. It uses KVM via a docker cap you give it permission for in the docker compose.

It should work with this Winapp thing, but I haven’t gotten much success so far trying to connect it. I’ve just been RDPing into them but I’d have liked to just pull the relevant windows alone, more like Terminal Service Applications.

https://github.com/dockur/windows

Yah, I dinked with this for far too long on several docker-based windows installs I have around the network including localhost on a non-standard port. Fails to set up and gives no messages to follow up when it does. I can connect to them fine with a normal xfreerdp command.

2/7