Search results for query: lxc

Yes - that script did ask that! I will try to re-install it again in a couple of days :) Do you know if that also will fix the "connection error" that I see Every couple seconds on the vms/lxc?

Still trying to learn this stuff, but I think the vm is not going to yield resources to other vm's if it's busy, whereas a lxc container will - Is this correct?

Hi Guys - Brand new to Proxmox, so apologies in advance if this is info posted somewhere (I had a look, but can't see it!) - is there a bit of a guess at the likely release date of Ubuntu 26.04 templates to use for LXC containers?

...and did perform the "PVE Post Install" but still have lots of issues with my Proxmox installation. What i want to create is a Nextckoud VM/LXC with the now 10TB that will increase in the future to like 20TB or 30TB. When i have the Nextcloud working i will get Nginx Proxy Manager installed...

So this is kind of sorted now (and it wasn't any of those things). The LXC is now at least backing up. Doing the exclusion file doesn't have any effect (I suspect that needs the actual PBS setup to work) - nor does (as I found elsewhere) editing a setting in /etc/vzdump.conf - it passes the...

...on Supermicro Epyc ROME platform (32-core, 384GB RAM, fast SSDs all direct-to-cpu. Running Proxmox 9.1 with Gnome DE and a mix of VM and LXC guests, with Incus and ssh2incus running in some VMs and possibly Podman with Devpod in others. Need to build an OOBM network across this infrastructure...

That is why I suggested: Anyway it seems that the OP has successfully solved the issue.

Ich denke du hast meine Frage korrekt beantwortet, und mein Lösungsansatz hat im Nachgang nicht funktioniert. :) Mit lxc-usernsexec werden die Berechtigungen im Container auf Berechtigungen außerhalb des Containers gemappt. Fehlende Berechtigungen sind häufiger ein Problem, wenn Zugriffe an...

Maybe a workaround: Find an LXC that does starts up fine at boot & then configure the order for that LXC to startup first, & then add a Startup delay to that container, so that the subsequent LXCs startup successfully. You could even create a "bogus" LXC just for this task.

I'm seeing the same issue, on a single LXC (running Plex) out of many LXCs and VMs. Here's my log, hope it helps...

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.