Not support with Proxmox

[RedxLus]

The uninstall wireguard make all proxmox unstable. Add img:

[Rebelllious]

I believe this can be tuned further to support Proxmox, but we would need more details on how exactly you were setting it up and what OS was used. Output of "source /etc/os-release" will be helpful, too.

[markc]

@RedxLus if you could add "set -x" to the top of the script and run it again (if possible) then that would show more details about why the script is attempting to remove a lot of PVE packages. The script is removing a dependency of the Debian PVE packages, but it's not obvious which package is causing this. I'm running WireGuard inside an Ubuntu container, but I can understand you may want a peer endpoint directly on the host.

~ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

[markc]

Here we go. Looks like the culprit is the qrencode package. Probably the best way to detect if Proxmox is installed on a Debian system is to check for the existence of /usr/bin/pveversion.

~ which pveversion
/usr/bin/pveversion

~ pveversion
pve-manager/7.2-11/b76d3178 (running kernel: 5.15.60-2-pve)

~ apt remove qrencode
Reading package lists... Done
Building dependency tree... 50%
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  proxmox-offline-mirror-docs proxmox-offline-mirror-helper
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  libpve-guest-common-perl* libpve-storage-perl* proxmox-backup-client* proxmox-ve* pve-container* pve-ha-manager* pve-manager*
  qemu-server* qrencode*
0 upgraded, 0 newly installed, 9 to remove and 0 not upgraded.
After this operation, 26.0 MB disk space will be freed.
Do you want to continue? [Y/n] W: (pve-apt-hook) !! WARNING !!
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
W: (pve-apt-hook) 
W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve' from your system, run the following command
W: (pve-apt-hook)       touch '/please-remove-proxmox-ve'
W: (pve-apt-hook) run apt purge proxmox-ve to remove the meta-package
W: (pve-apt-hook) and repeat your apt invocation.
W: (pve-apt-hook) 
W: (pve-apt-hook) If you are unsure why 'proxmox-ve' would be removed, please verify
W: (pve-apt-hook)       - your APT repository settings
W: (pve-apt-hook)       - that you are using 'apt full-upgrade' to upgrade your system
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook

[Prajwal-Koirala]

Regarding the issue of WireGuard causing instability on Proxmox when uninstalled, as reported in your GitHub repository issue #331, several key points and suggestions have been made by contributors.

1. The original issue was raised by a user who noted that uninstalling WireGuard made the entire Proxmox system unstable【6†source】.

2. A contributor suggested that more details about the setup and the operating system used would be helpful to address the issue. Specifically, they requested the output of "source /etc/os-release" to understand the environment better【7†source】.

3. Another contributor recommended adding "set -x" to the top of the script and running it again. This action could provide more detailed information about why the script is attempting to remove a significant number of PVE packages. They noted that the script appears to be removing a dependency of the Debian PVE packages, but it wasn't clear which package was causing this issue【8†source】.

4. Finally, it was identified that the qrencode package might be the culprit. It was suggested that to detect if Proxmox is installed on a Debian system, checking for the existence of /usr/bin/pveversion could be an effective approach【9†source】.

To address this issue comprehensively, consider the following steps:

• Gather more detailed information about the environment where the issue occurs, including the specific OS and Proxmox versions.
• Implement the suggested script changes (like adding "set -x") to gain more insights into the uninstallation process.
• Investigate the role of the qrencode package and how its removal impacts Proxmox.
• Consider setting up a test environment to replicate and resolve the issue without affecting a production system.