The post you responded to is 2 years old.
That said, /etc/pve directory isn't a real directory, it is a fuse mount of a database. So you probably should be excluding it from etckeeper. I don't use that software so can't tell you how to do it...
It looks like you have repositories configured in both /etc/apt/sources.list and /etc/apt/sources.list.d. Having everything in the sources.list file is the "old way" while files in /etc/apt/sources.list.d is the "new way".
I suggest to...
Well, it is incorrect to have both regardless of why you did it and now you have a different set of errors. Fix that and post the results of what @Neobin asked for.
The most common reason for the error you are getting is incorrect repositories...
Proxmox VE can be configured to update automatically (see "apt info unattended-upgrades"). This is a Debian feature and I think there are good reasons for it to not be enabled by default (e.g. you don't know what else the admin has installed, do...
I disagree. I think it's more toxic to have EOL systems (like PVE7) on the Internet. It makes the world for all a worse place. I also think it's toxic to register accounts to cry about about an "Proxmox security issue" which quite obviouvsly...
Systems without current system updates can be hacked, nothing is "new" or "urgent" on this. And PVE7 and PVE8 won't get any security updates any more so it's somehow expected that they get owned. Even if you don't connect them directly to the...
Only to you, unless you are claiming that it affects an up-to-date version of PVE.
PVE 7 is based on Debian 11, PVE 8 on Debian 12. So they would be affected by that bug unless they were updated since the bug was fixed.
I guess you mean you're amazed that whatever is writing these broken VMDK files isn't fixed.
If a field is supposed to be quoted, and isn't, that's not a problem with the parser, it is a problem with the writer. The only complaint you should...
ZFS “must” always be able to fully see the drives. If it doesn't, or only partially does, problems usually arise. See also the documentation here: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_hardware_2
Do not use ZFS on top of a...
On the master that is serving time to clients you need the "allow" line at least. In addition, IF the master does NOT have NTP available and you want to use the local clock instead, then you also need "local", but the stratum needs to be less...
Most NTP servers will say their time is invalid or a high stratum unless they are synchronized to an external source like another NTP server or a GPS clock. One common symptom of this is that the clients of that server will refuse to synchronize...