Search results for query: lxc

We've got several containers failing to start at host reboot (they are configured to start at boot, any order). Each of them gives an identical error in the UI (aside from container #): However, the affected containers will start manually afterward. These containers include nvidia-device...

...ZFS volumes are not touched by zfs rewrite. They must be handled via zfs send/receive, best with an interspersed "pv -b 1G" on spinning disks. 6. LXC subvols are often not worth the effort, because they take ages to convert while the container must be stopped. The space of these will...

...switch, I have VLAN8 set as the native untagged VLAN passing to my two Proxmox nodes. I am passing a few VLANs as tagged through to Proxmox for LXC and VMs. In Proxmox VE, I have vmbr0, vlan aware, set with static IPs in VLAN8. I also have a Linux VLAN setup in Proxmox for communication with...

That is what I said here. As I said here also, you might be able to exclude it (even though I cannot explain why it is not excluded automatically). Maybe someone else knows? The "backup feature build into proxmox itself" can also backup to PBS. I agree that the actual type of the destination...

So you are backing up to a file on a directory storage and not to PBS? Yes. Maybe not what you want but it would be an interesting data point to try (once). Maybe check the file owner, group and permission from the Proxmox host? My unprivileged container with snap when backed up from PVE to...

...reason. So I redacted the snap names... This is the latest version of Proxmox using the backup tool built into the system. So just selecting the LXC's from the list and then going ahead on the default settings. If I try the stop mode as you suggest does that mean the LXC needs to be stopped...

Just looking into the integrated Proxmox backup on my host and it seems LXC backups are working fine but when the LXC includes a snap then it is failing like so: ERROR: rsync: [sender] readlink_stat("/proc/3691699/root/snap/xxx/2411") failed: Permission denied (13) ERROR: rsync: [sender]...

...pve2 --notes-template '{{guestname}}' --remove 0 --storage pbs100G --notification-mode notification-system INFO: Starting Backup of VM 300 (lxc) INFO: Backup started at 2026-04-25 16:29:38 INFO: status = stopped INFO: backup mode: stop INFO: ionice priority: 7 INFO: CT Name: dev INFO...

...Dateien, die im Backup 110 nicht vorkommen. Das kann sehr gefährlich sein! rsync -avv --delete /mnt/restore-ct-110/etc/openvpn/ /var/lib/lxc/111/rootfs/etc/openvpn/ rsync -avv --delete /mnt/restore-ct-110/etc/pivpn/ /var/lib/lxc/111/rootfs/etc/pivpn/ 6. Setzen der richtigen Berechtigungen...

...net.ipv6.conf.all.forwarding = 0 ❯ sysctl net.ipv6.conf.vmbr0.forwarding net.ipv6.conf.vmbr0.forwarding = 1 ❯ sysctl net.ipv6.conf.vmbr0.accept_ra net.ipv6.conf.vmbr0.accept_ra = 2 But issue remains. Restarting an LXC resolves the issue temporarily for that LXC. Same for host.

Johannes, thank you, I already have PBS on a separate machine, with a hardware raid backup disk and an iSCSI mount to a QNAP NAS. My entire cluster runs on Intel Mac Mini's, on eBay, around 50-60 GBP, up to 16GB RAM, any size SSD you can afford, I7 quad core/8 thread if you can find them, low...

A workaround for the free -h command displaying incorrect memory statistics in an Alpine Linux LXC container is to install the procps with apk add procps, because the default busybox version of free fails to read cgroups right, but the procps version does. It also fixes top. However, the podman...

My issue has nothing to do with LXC. At least for me. I am only using a VM.

This might not be an issue with LXC? I really need a 26.04 lxc template. :) Is it possible to create already?

Das war eine Configzeile wo ich AppArmour etwas begrenzt hatte lxc.apparmor.profile: lxc-container-default-with-nesting

OT - welche Config ist das genau?

...1.3.0 libpve-notify-perl: 9.1.2 libpve-rs-perl: 0.13.0 libpve-storage-perl: 9.1.2 libspice-server1: 0.15.2-1+b1 lvm2: 2.03.31-2+pmx1 lxc-pve: 6.0.5-4 lxcfs: 6.0.4-pve1 novnc-pve: 1.6.0-4 proxmox-backup-client: 4.1.8-1 proxmox-backup-file-restore: 4.1.8-1 proxmox-backup-restore-image: 1.0.0...

...failed to apply acls: EINVAL: Invalid argument Logical volume "vm-110-disk-0" successfully removed. unable to restore CT 110 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client restore '--crypt-mode=none' ct/110/2026-04-17T01:00:25Z root.pxar...

Thank you for the clarification! I just wanted to know if they were viable options for migration from a Windows OS to a more cost/efficient one.

...seperation it might make sense to install the ProxmoxBackupServer and PVE bare-metal together on the node and afterwards setup a small Debian lxc or VM just for the qdevice. Note that you don't install the PBS as vm, the idea is to be able to have working restores even if the PVE breaks for...