I am installing Proxmox from the repositories over a fresh Debian bullseye-backports image. I'm using this cloud image daily build:
https://cloud.debian.org/images/cloud/bullseye-backports/daily/latest/
The specific version of the image is: debian-11-backports-genericcloud-amd64-daily.qcow2
I am encountering one single issue during install that I cannot solve. While installing
How can I correct for those two problems with
I also encountered three other of what appeared to be problems, but I have solved them, I think.
The first is this one:
According to this post by Proxmox staff, this is cosmetic and can be ignored. I assume that this complaint is that the directory is not found, but the install process does create it correctly. Therefore it can be ignored. Please let me know if I am incorect in my interpretation of this problem.
The last two are both related. The cloud image requires cloud-init for it to boot properly for the first time. After that, it is not needed. There are two package dependency conflicts with Proxmox packages and base system cloud-init packages. Here are the two sections of the install log where this occurs:
My solution here is to uninstall cloud-init and cloud-image-utils before installing Proxmox:
This appears to fix the problem. Let me know if this is the wrong way to fix this issue and what the better way might be.
https://cloud.debian.org/images/cloud/bullseye-backports/daily/latest/
The specific version of the image is: debian-11-backports-genericcloud-amd64-daily.qcow2
I am encountering one single issue during install that I cannot solve. While installing
lxc-pve
package, the following is happening:
Code:
Setting up lxc-pve (5.0.0-3) ...
apparmor_parser: Unable to replace "/usr/bin/lxc-start". Profile doesn't conform to protocol
apparmor_parser: Unable to replace "lxc-container-default". Profile doesn't conform to protocol
Created symlink /etc/systemd/system/multi-user.target.wants/lxc-monitord.service → /lib/systemd/system/lxc-monitord.service.
Created symlink /etc/systemd/system/multi-user.target.wants/lxc-net.service → /lib/systemd/system/lxc-net.service.
Created symlink /etc/systemd/system/multi-user.target.wants/lxc.service → /lib/systemd/system/lxc.service.
How can I correct for those two problems with
apparmor_parser
?I also encountered three other of what appeared to be problems, but I have solved them, I think.
The first is this one:
Code:
Setting up swtpm-tools (0.7.1~bpo11+1) ...
Adding group `tss' (GID 119) ...
Done.
Warning: The home dir /var/lib/tpm you specified can't be accessed: No such file or directory
Adding system user `tss' (UID 112) ...
Adding new user `tss' (UID 112) with group `tss' ...
Not creating home directory `/var/lib/tpm'.
According to this post by Proxmox staff, this is cosmetic and can be ignored. I assume that this complaint is that the directory is not found, but the install process does create it correctly. Therefore it can be ignored. Please let me know if I am incorect in my interpretation of this problem.
The last two are both related. The cloud image requires cloud-init for it to boot properly for the first time. After that, it is not needed. There are two package dependency conflicts with Proxmox packages and base system cloud-init packages. Here are the two sections of the install log where this occurs:
Code:
dpkg: ifupdown: dependency problems, but removing anyway as you requested:
cloud-init depends on ifupdown.
(Reading database ... 21599 files and directories currently installed.)
Removing ifupdown (0.8.36+pve2) ...
Selecting previously unselected package ifupdown2.
dpkg: qemu-utils: dependency problems, but removing anyway as you requested:
cloud-image-utils depends on qemu-utils.
(Reading database ... 23021 files and directories currently installed.)
Removing qemu-utils (1:5.2+dfsg-11+deb11u2) ...
Selecting previously unselected package pve-qemu-kvm.
My solution here is to uninstall cloud-init and cloud-image-utils before installing Proxmox:
Bash:
apt-get purge -y cloud-init cloud-image-utils
apt-get autoremove -y
apt-get install -y proxmox-ve
This appears to fix the problem. Let me know if this is the wrong way to fix this issue and what the better way might be.
Last edited: