Search results

I have a similar (I think) issue. Often when backing up an LXC that is using a nfs mountpount passed through from the host PVE, the backup job gets stuck at "INFO: create storage snapshot 'vzdump' and the entire node ends up with a question mark on: It seems Proxmox does not handle mount...

For me, zfs set acltype=posixacl rpool/ROOT/pve-1 was the solution.

I fixed this anyway by starting my LXC. That seem to allow PVE to back it up without this error. I don't know why. Another day, another generic "255" error code...

@fabian fair enough,I apologise. But when the Proxmox UI throws this error, and literally the ONLY thread on Google is this thread, your post doesn't give any clarity as to how to diagnose or solve the issue, or even the root cause. I have a standard OOTB LXC and it's throwing this error...

What does this even mean? How is it related to an LXC backup? What dataset? What zfs dir? I'm not sure what this advice means in the context of "my LXC failed to backup with the following error"

I gave up running docker in LXC with ZFS. You end up compromising somewhere (stability, or losing pve snapshot/replication features). I'm still hopeful one day it will be solved. I've moved most of my apps running in VM docker containers to LXCs, by studying their dockerfiles, but for some it's...

To be honest, it is ridiculous that a command labeled as "Stop VM immediately" can be blocked by a failing "reboot" command. A "stop" command should be able to supersede any soft ACPI shutdown signals. Categorically not true - if the VM is locked by a failing soft ACPI shutdown/reboot, it...

Thanks @fabian, appreciated! Absolutely, it is a shortcoming in my knowledge of LXC's - from what I've read they are being positioned as a lightweight alternative to VM's and the word isolation appears multiple times in any article or definition of them. I guess here be dragons applies to LXC...

Proxmox is free to make recommendations on how to best run Docker. But LXCs are a container technology, and especially when running in unprivileged mode, should not impact a host system. To some degree, it's unimportant what is running inside an LXC or a VM, if a container is escaping its...

I would have thought unprivileged LXC containers crashing a Proxmox node is quite the urgent bug. Happy to provide more info.

This issue is persistent on my 3 cluster node. I delete the replication job...it comes back with errors a few days later. Happens across all my VM's and replication tasks.

@Helmut101 BTW based on my recent findings I currently would not advise using LXC in Proxmox *at all*. I have shared the issue here: https://forum.proxmox.com/threads/unprivileged-lxc-container-eventually-locks-up-pve-host-processes.108362/ But tl;dr unprivileged LXC containers using FUSE are...

I am running 2 unprivileged LXC containers on a proxmox-ve 7.1-1 (running kernel: 5.13.19-3-pve). Both lxc's are running docker. The only "exotic" about it is using Fuse for the docker filesystem. The have nesting,keyctl,fuse,mknod =1. They run fine for hours, sometimes days, but after a while...

@Helmut101 you are welcome! I finally got docker working in LXC thanks to you :) I just got the LXC snapshot error again: failed to open /var/lib/docker/fuse-overlayfs/4da3c0b5f7c487e8ca3d7849ccfa7218b41ef3b94be2dc7c6ea4eb330159e005/merged: Permission denied TASK OK It actually seems like...

Just had an issue with Proxmox snapshot / docker / fuse. When doing a snapshot I got an error about not being able to read /var/docker....../fuse or something. I then rolled back, and although the image was rolled back the Proxmox rollback UI did not reflect which was the current state. Tried...

Gosh, why is this all so hard? :) LXC will not get widespread adoption with so many pain points OR until there is a simple way to convert docker to lxc (there are instructions available..but it's full of errors and issues). @Helmut101 your blog post is super helpful thank you! For me however...

@t.lamprecht you're absolutely right - apologies. This thread is full of red herrings that mask the underlying cause.

Thank you @meckanism ! Finally after 3 years of random HA boot failures with this error, this works to fix it!!

This is still an issue in 2022....the homeassistant VM will suddenly stop booting with this "failed to load boot001 uefi qemu not found" error. It's all related to the efi disk, and none of the suggestions here help (in particular the OVMF/UEFI Boot Entries article "Boot Maintenance Manager" ->...

Sure but it contains errors. "sed -i -e 's/buster/bullseye/g' /etc/apt/sources.list.d/pve-install-repo.list" This file doesn't exist, and isn't mentioned anywhere in the linked to Package Repositories documentation. The commands above from @ermanishchawla work though.