Search results for query: lxc mountpoint

Hi, I know I'm late to the party but I've had 2 real headaches on our cluster: We use containers, a lot of containers running special applications which in some cases are stuck on older versions of Linux, like CentOS7, (Systemd woes) We use a few containers running a hosting-environment...

Hi everyone, I have my Proxmox running on the old Samsung SSD 860 EVO which seems to be failing. I couldn't create a new container today and running a SMART check on /dev/sdb shows errors and bad blocks. I have some VMs on this disk but they are backuped and not really critical so I don't mind...

The original post worked well for me. Thx @TheHellSite One suggestion I would give is to run on host to add same group name using gid on host by running : addgroup --gid 110000 lxc_usershare Makes it easier to add it to directories that needs to be accessed by LXCs. Hope this isn't a bad...

@bluesite hat das wahrscheinlich richtig erkannt, /dev/sda vs /dev/sda1 ist nen Klassiker. @Xande, falls du das auf dem Wyse 5070 nochmal mit Proxmox versuchst: auf dem Host per fstab mounten und dann als Mountpoint in die LXC-Config, nicht aus dem Container heraus. Viel Erfolg!

Read a bunch of posts about this, tested it, both work to the point that the data in the share is exposed to the Unpriv LXC in both cases. Wondering what the delta in functionality / risk is? Proxmox 9.1.4, 3-host cluster (identical hosts) Method 1: Host Mount + Bind Mount (recommended in...

Ich hätte vielleicht ein bisschen erläutern sollen worum genau es mir ging. :) Sollte im Endeffekt nur bedeuten, dass man für den Mountpoint eines LXC zuerst einen Standardeintrag in der "fstab" erstellt, wie bei so gut wie jeder anderen Linux-Distro. Dass man diesen dann auch über die GUI...

This guide explains how to get GPU accelerated applications and full desktop-remoting with unprivileged containers working. It further explains how to get nested containers to run. This not only includes things like docker, podman or kubernetes but also flatpaks as these too -by their use of...

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.