Recent content by DVDIsDead

docker sets up some iptables rules, borks everything, in the name of security i believe. info i used to solve: https://docs.docker.com/network/packet-filtering-firewalls/#docker-on-a-router...

sudo systemctl edit docker add this: [Service] ExecStartPost=iptables -I DOCKER-USER -j ACCEPT save reboot probably a huge security risk or wahatever, and not recommended see above. but it works for me

Afaik that is correct, attempting to change the hostname of a host that is set up is not supported, or recommended. but if you back up your containers and vms, reinstall, and do the steps laid out in the comment above yours, you can restore the containers afterwards no problem. Unless you...

the wiki does say "This must be done on a empty node." at least it does at the time of writing. best way i know of (fresh install, before first boot): - uncheck automatically reboot after successful install, - ALT+<Fkey> when its done for a command line - nano the files: nano /etc/hosts...

getting an error restoring a container. from googling it said the solution was to restore as privileged instead of unprivleged, but both cause the same error: recovering backed-up configuration from 'raid1-backups:backup/vzdump-lxc-125-2022_11_11-21_09_34.tar.zst' WARNING: You have not turned...

i had tried all three, all did the same error. i fixed it though: i had to stop the container, mount the disk image file in a tmp directory, and remove (container root)/dev/lxc-125.log, which was not present when the container was running.

no change, but I just realized the console in proxmox web interface no longer works for any container however SSH works fine: failed waiting for client: timed out TASK ERROR: command '/usr/bin/termproxy 5900 --path /vms/125 --perm VM.Console -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole125 -r...

nope. its a btrfs raid1 array, and other containers backup to it regularly

INFO: starting new backup job: vzdump 125 --notes-template '{{guestname}}' --remove 0 --compress zstd --mode stop --node pve --storage raid1-backups INFO: filesystem type on dumpdir is '-' -using /var/tmp/vzdumptmp4105384_125 for temporary files INFO: Starting Backup of VM 125 (lxc) INFO: Backup...

as per https://pve.proxmox.com/wiki/IO_Scheduler I tried checking available io schedulers for my drives, they all only specify mq-deadline and none. ``` root@pve:~# cat /sys/block/sda/queue/scheduler [mq-deadline] none root@pve:~# cat /sys/block/*/queue/scheduler none none none none none none...

did you change the permissions of /dev/net/tun? using cgroup2 solved my issues (also after migrating to a PVE 7.1 node)