Search results

please check with "ls -la"

you don't need execute that file, docker auto-detect that and use it.

Download the "fuse-overlayfs-x86_64" file, move to "/usr/local/bin/fuse-overlayfs" and make it executable.

Google Translator: I think their "product" will not take off. Everyone will understand why, well, except for those who want to stay on a normal platform but at the same time comply with the law. As it appeared, so it will die.

Have you tried with pve-kernel-5.13?

ja, genau

mit "systemctl suspend" über ssh zb.: ssh root@pbs -i ~/.ssh/id_rsa_pbs 'systemctl suspend'

mit pve-manager 7.1-11 und "job-init" Hook funktioniert: vzdump-hook-script: #!/bin/bash if [ "$1" == "job-init" ]; then etherwake XX:YY:ZZ:XX:YY:ZZ ping -W 20 -c 1 pbs-test.lan /usr/sbin/pvesm set pbs-test -disable false fi exit 0

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