Search results for query: lxc mountpoint

A reboot of the LXC Container does NOT work for me. I need to first stop the LXC Container. Wait a few seconds. Then start the LXC Container again. In a normal Situation, the Share is already mounted on the Host. The only "Fix" I could find for the initial (after Host Boot) is: pvenode config...

I use lxc.mount.entry: /dev/dvb dev/dvb none bind,create=dir 0 0, which sometimes disappears on host and gets recreated. A reboot of the container (afterwards) works fine. Have you tried using a hookscript to make sure the host mount is done pre-start and umount done post-stop? EDIT: I think it...

I am trying to understand a bit better the Security Architecture of using LXC Unprivileged Containers. I am familiar with Virtual Machines (KVM) and also Podman Containers (similar to Docker), but relatively recently I've been deploying quite a few LXC Unprivileged Containers, I can...

Servus! Ich habe einen LXC container laufen mit einem konfgurierten Mountpoint mit größerem Speicher. Leider sehe ich nirgends in der Webgui, wie ausgelastet das CT-Volume ist. Mir wird ja nirgends der freie Speicherplatz angezeigt. Nur unter "Storage" sehe ich den verfügbaren Speicherplatz...

Her is some Feedback after doing some Experiments: Changing the Owner/Permissions of the mountpoint in the container while it's not mounted works. The correct solution would probaply be the idmap shenanigans. But that's for another time. For now I went with a different Solution: On the Host...

Hallo, ein kürzliches Systemupgrade (PVE 9.1) lies einen Container nicht mehr starten. Die Fehlerausgabe: lxc-start: 10105: ../src/lxc/utils.c: run_buffer: 571 Script exited with status 30 lxc-start: 10105: ../src/lxc/start.c: lxc_init: 845 Failed to run lxc.hook.pre-start for container "10105"...

Confirm this problem mounting a rw volume as a ro=1 mp after the most recent apt-get full-upgrade No documentation about the "Enable idmapped mounts" is provided and the syntax given here doesn't work. Starting the container with debug results in lxc-start 108 20260208150732.185 DEBUG utils...

I confirm I was also just affected by this I opened another Issue a few Minutes ago about it: https://forum.proxmox.com/threads/lxc-fails-to-start-when-using-read-only-mountpoint.180440/

I have a Mountpoint /tools_nfs that is mounted read-only on most of my Systems, and I want to be able to pass it to each Container. It used to work OK until now. I suspect one of the last System Updates messed it up :( . Attached is the Debug Log obtained by lxc-start -F --logpriority=DEBUG...

The change log of pve-container 6.1.0 mentioned something about using the owner/group of a mountpoint if the directory already exists in the container before mounting. Maybe remove the directory inside the container with the mountpoint temporarily disabled? Or change the owner/group (inside the...

FYI this also affects ceph bind mounts. (I think it's the same underlying issue so I won't open a separate thread/report.) Relevant config (readonly mount point): mp0: /mnt/pve/cephfs-hdd/dump,mp=/cephfs-hdd-backups,backup=0,ro=1 Starting container: # pct start 105 --debug run_buffer: 571...

Where and what would be the correct process in raising a bug report (I have never done one before :confused:) I have updated the entire cluster(bar pve-container since it was causing an issue due to another bug meaning I couldn't start containers with bind mounts) and TrueNAS to 25.10.1 and...

See some of the threads about "LXC with mountpoint not starting anymore" in the last few days: https://forum.proxmox.com/search/9021402/?q=lxc+mountpoint&o=date EDIT: I did not run into this issue myself, but reinstalling the previous version of the pve-container package appears to be a work-around.

I'm trying to get my Audiobookshelf LXC to be able to migrate between my two nodes, but I'm running into issues. I want the LXC to have a mountpoint pointed at a NFS share on my NAS, where I keep my auidiobooks, but when it has the mp0: set, migration fails with the error: cannot migrate local...

Maybe this can be fixed by removing the code that's causing this issue in /usr/share/perl5/PVE/LXC.pm: PVE::Tools::fchownat(fileno($mount_fd), '', $uid, $gid, PVE::Tools::AT_EMPTY_PATH) or die "failed to propagate uid and gid to mountpoint: $!\n"; Feel free to test. There is no official...

Hello all, I have the following configuration (and similar like it) for a lot of my LXC containers: ./209.conf:mp0: /mnt/glusterfs/hub-volume/andrewcz-org/firefly-importer_uploads,mp=/var/lib/firefly-importer/data/storage/uploads ./209.conf:mp1...

I think I have a similiar configuration running for a long time without serious issues. However I am still on TKFS 16 (LXC no. 105). I am backing up the Data with rsync to an external USB drive. I am now experiencing long waiting times whenever MacOS computers try to access a samba share, even...

I have a similar issue but I don't think the patch will fix it, it's related to propagating UID and GID on a mountpoint. Had issues on 6.1.0, downgrading to 6.0.18 fixed it. Logs: run_buffer: 571 Script exited with status 1 lxc_init: 845 Failed to run lxc.hook.pre-start for container "115"...

After running apt upgrade and rebooting, my mountpoints on LXC containers behave differently: 1. Regular mountpoints keep getting mounted as root:root, e.g. /var/lib/mysql, preventing MySQL from starting. 2. Read-only mountpoints prevent the LXC container from starting entirely. Regular...

After updating yesterday I woke up to half of my containers refusing to start after they were backed up overnight. run_buffer: 571 Script exited with status 1 lxc_init: 845 Failed to run lxc.hook.pre-start for container "122" __lxc_start: 2046 Failed to initialize container "122" TASK ERROR...