Zoker's latest activity
-
ZZoker replied to the thread [SOLVED] Upgrade hangs with "Setting up pve-manager (9.0.17) ...".Hi @Onslow Yes sure, so here is a list of the relevant processes on my system: root@jupiter:~# ps auxf | grep -A 5 dpkg root 11328 0.0 0.0 11988 6264 pts/0 T 15:05 0:00 \_ dpkg --configure -a root 11375 0.0...
-
ZZoker replied to the thread [SOLVED] Upgrade hangs with "Setting up pve-manager (9.0.17) ...".Ok after some more investigation I was able to fix it by running these commands: kill -9 13337 kill -9 11328 rm /var/lib/dpkg/lock-frontend rm /var/lib/dpkg/lock dpkg --configure -a After that the updates went through
-
ZZoker posted the thread [SOLVED] Upgrade hangs with "Setting up pve-manager (9.0.17) ..." in Proxmox VE: Installation and configuration.Hi there, Today I ran a update, which does not seem to be sucessfully. Everytime I try to upgrade, the process hangs at the root@jupiter:~# dpkg --configure -a Setting up pve-manager (9.0.17) ... I tried to wait for an hour, but nothing...
-
-
ZZoker replied to the thread [SOLVED] Docker inside LXC (net.ipv4.ip_unprivileged_port_start error).Thanks for the hint! I enabled the test repo and then run this command: apt update apt install --only-upgrade lxc-pve And after that disabled the repo again. Works like a charm, thanks!
-
ZZoker replied to the thread [SOLVED] Docker inside LXC (net.ipv4.ip_unprivileged_port_start error).Yea that's the same what I did now. Only think I'm wondering is, that I did not update any package within my LXC container and the issue still occurs. Is it an option to install an old containered.io package version?
-
ZZoker reacted to rodoprox's post in the thread [SOLVED] Docker inside LXC (net.ipv4.ip_unprivileged_port_start error) with
Like.
I disabled AppArmor within LXC config as my container is trusted and not exposed directly to the internet. -
ZZoker replied to the thread [SOLVED] Docker inside LXC (net.ipv4.ip_unprivileged_port_start error).Does anyone have a solution for alpine os? I have containerd.io version 2.1.3-2 installed (which is not the latest version), but I still have this issue.
