Recent content by Helmut101

overlay2 fs ist der Standard. Ich würde von ZFS nativ als Docker fs in unprivileged LXC/nested auch heute noch abraten.

Coming back here to confirm reboot worked :thumbsup: I think this line in the documentation indicates that "System currently booted with legacy bios" is Ok: > In the end, both legacy BIOS or UEFI can use this setup for booting.

I hit the issue where `grub-probe` complains with "error: compression algorithm inherit not supported", likely because sanoid did a snapshot of my ZFS root/boot partition, as described here: https://github.com/openzfs/zfs/issues/15261 I followed...

Just upgraded and everything worked fine (Xeon E3-1230 v3 from 2013). I did add network name overrides, as suggested, before doing the upgrade. 1. Get Mac address `watch ip link` for eno1 and eno2 2. Create links for the two network cards in my sys, with priority 10 and 20: - avoid eno1 and...

Wow, this hit me hard, too. Had this on my offsite ZFS backup, where I received ZFS datasets/snapshots with Syncoid. This was really tricky to identify, thank you for reporting!

Thank you. I think I tend to do the following: - keep automated, full snapshots using the PVE snapshot utility (will create tar's of VMs/LXC etc., properly suspend guests etc.) - install Sanoid on Proxmox itself, create automated inexpensive ZFS snapshots of all datasets, including VM disks but...

Did you every find an answer to this? I am at the same stage, trying to setup sanoid in a privileged LXC on Proxmox, to not dirty the Hypervisor. I have set up Syncoid in Pull mode, with a specific user on the Hypervisor that is limited in rights using ssh command restrictions, so I am only...

Just updated to 8.0.3 and everything went smooth on my single-node, 20x LXC, nested Docker, zfs-backed Proxmox! All services ran immediately as if nothing happened.

You need to build these containers on LXC itself, this will prevent UIDs to be out of range.

Looks good Neuer_User, I will definitly try this again! Thanks for sharing.

I'll need to look into this more closely, but it follows what I described here https://du.nkel.dev/blog/2021-03-25_proxmox_docker/ .. and it has worked flawlessly since 3 years, tested up till the current Proxmox 7.3-4. The latter steps look like this is solving the migration issue, thanks for...

> warum um alles in der welt will man docker in lxc containern laufen haben, wenn es dauernd bei updates kaputt geht und "strongly discouraged" ist ? Da gibt es mehrere, jeder muss selbst entscheiden: 1. Ressourcen: Ich habe bei mir nur 32GB RAM ohne Möglichkeit auf zeitnahes (< 2 Jahre)...

I like the basic approach from Proxmox. You can extend sensor collection yourself, just set up Telegraf & InfluxDB, e.g. Proxmox Hypervisor Monitoring with Telegraf and InfluxDB.

Great, thank you. Very informative. My server is only available locally/IPsec/vpn, Services are further separated in several VLANS and firewalled in a Demilitarized Zone (only response allowed). Otherwise, I would also prefer VMs.

Yes, I think I monitor host bytes, the Evo attribute is called "Total_LBAs_Written" and the WD reports "Host_Writes_GiB". Most of my DBs do 90% read and only rarely write, so this makes sense. I also have encryption+compression enabled on all my pools. Interesting..