Search results

Genau, so habe ich es vorgestellt. :) Danke Fabian.

Ich habe gedacht, storage aktivieren, pbs aufwecken, mit "hook script" könnte auch funktionieren. Leider nicht... Währe logisch im vzdump den job-start hook Abruf ganz vorne schieben, vor storage prüfungen...

Bei mir funktioniert es leider nicht. Es sieht so aus, vzdump hat volgende grundsätzliche Voraussetzungen (vor dem "job-start" Hook): 1. aktivierte Storage, sonst Fehler: "TASK ERROR: could not activate storage 'pbs-test': storage 'pbs-test' is disabled" 2. erreichbare Storage, sonst Fehler...

ok, you don't need my help, good luck!

you can try restore the backup under commandline with: "pct restore" command with "ignore-unpack-errors" flag https://pve.proxmox.com/pve-docs/pct.1.html

if originaly was Unprivileged (you can check on backup under "Show Configuration"), than simply add "unprivileged: 1" to your conf file...

if your container originaly was Unprivileged than you need set the "Unprivileged container" to Yes maybe you deleted the line "unprivileged: 1" from your conf file

try reinstall docker: https://docs.docker.com/engine/install/debian/

check with "journalctl -fu docker"

this is ok, sorry... lxc started without error. please start with "pct start 108", check in container "systemctl status docker.service"

please change "cgroup -> cgroup2" again, because you have been overwritten...

please stop the container with "pct stop 108" and try again

start the container with the following command and post the "/tmp/lxc-108.log" lxc-start -n 108 -F -l DEBUG -o /tmp/lxc-108.log

change in your LXC config "lxc.cgroup" to "lxc.cgroup2" https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Old_Container_and_CGroupv2

"Re-create the MS DTC log" und "Re-registering the service": https://answers.microsoft.com/en-us/windows/forum/all/error-8004e00f-when-trying-to-access-com/782e5a36-d28f-4b35-a53c-f343e456638d

Komisch, bei mir "qemu-ga-i386.msi" und "qemu-ga-x86_64.msi" im "virtio-win.iso" sind anders (siehe Änderungsdatum)... Probiers mal noch einmal herunterladen...

try your debian container (if not already set) with Features: nesting=on

I use snapshot for backup. Yes it is like a communication/networking problem. Dumb question: is your pbs/proxmox up to date?

I use also fuse-overlayfs for one of my Docker Container and PBS Backup working without problems. Except only a couple warnings: "failed to open /var/lib/docker/fuse-overlayfs/b4e3f337e5fb6b2517e1a85bab9e78235b97a501b6984525dd5cf6778a2a1dfb/merged: Permission denied" Proxmox: single node, no...

try with fuse-overlayfs: https://c-goes.github.io/posts/proxmox-lxc-docker-fuse-overlayfs/