Search results for query: lxc

...When I booted with kernel 6.17.4-2-pve, the pfSense instance worked as usual again. Another problem: I have a Splunk instance running on an lxc container. Unfortunately, I can no longer access the web interface. After a long time, the login page appears, but I cannot log in. But that may be...

...s3) but also has it's own http-based server: https://github.com/restic/rest-server You could install it beside the PBS on your PBS or create a lxc/vm with it in your regular Proxmox environment and afterwards back that up with PBS. Another option would be rsnapshot which works with ssh and...

Man.. I am still seriously struggling with getting this working. Even went so far as to give my user and token admin privileges on / and i'm still getting the same dang API Error: Unsupported service endpoint. I'm at a loss here. EDIT: Oh my fucking god, I fixed it. My original YAML -...

I am encountering a similar issue while testing Docker inside an LXC container. My environment is an unprivileged LXC running Ubuntu 25.04 on a Proxmox 8.4.9 host (Kernel 6.8.12-13-pve). I have already applied the suggested kludge via systemctl edit docker to include...

Schönen Dank dafür! :O) PS: .. brauche etwas Zeit, es auzuprobieren - schön, daß es nun auf der NPU unter Linux und auch in einem LXC auf Proxmox läuft!

...musste ich auf dem Host die beiden oben erwähnten Treiber installieren. Für den anderen Memlock limit Fehler müsstest Du in der Config des LXC Containers die folgenden Zeilen hinzufügen. arch: amd64 cores: 6 dev0: /dev/dri/renderD128,gid=993,mode=0660 dev1: /dev/dri/card1,gid=44,mode=0660...

...(via BIOS-Firmware Update?) zu sein, und separat installierte Treibermodule (amdgpu/amdxdna) am Host, da mit aktueller fastflowlm Installation im LXC Container folgender Fehler erscheint: flm validate [Linux] Kernel: 6.17.4-2-pve [ERROR] NPU firmware version on /dev/accel/accel0 is...

...I wanted to include my findings. Mainly because I found this post useful to me in narrowing down my issue. My setup and versioning: PBS 4.1.4 LXC (docker) homepage v is 1.10.1 The curl command from @meyergru was helpful for me because I kept getting permission check failed. I kept running...

...suffering this bug: Hardware: Proxmox host CPU: AMD Phenom II X6 1090T (AM3) Proxmox host RAM: 32GB ECC DDR3 NVMe: WD Black SN7100 1TB (VMs/LXC storage) NFS server: Debian 13 VM running inside the same Proxmox host, ZFS RAIDZ1 4×14TB (passed through), 16GB RAM, ZFS ARC limited to 10GB...

I still have MAC learning enabled. Then I took the following steps: - Completely restarted PVE - Logged in to LXC 202 via SSH - I find 3 entries for the MAC of LXC 202: $ bridge fdb show |grep -i BC:24:11:EE:DE:E3 bc:24:11:ee:de:e3 dev fwln104i0 master fwbr104i0 bc:24:11:ee:de:e3 dev veth202i0...

...folders and you don't really have control over it: 10.19.0.12:/mnt/user/htpc/ /mnt/pve/htpc/ nfs defaults 0 0 Then mount it into the LXC: mp0: /mnt/pve/htpc,mp=/data2 Now, with everything working and permission dramas solved, I wanna move ~800GB from the local SSD to the unRaid NFS shared...

Okay war mein Fehler, es läuft nun über die NPU im Priviliged LXC Container. Hab in openWebUI die URL zu FLM fälschlicherweise unter Ollama hinterlegt und nicht unter OpenAI.

...- https://github.com/amd/xdna-driver?tab=readme-ov-file#linux-compilation-and-installation und im LXC Container in dem FastFlowLM installiert ist kommt bei der Validierung nun auch das richtige Ergebnis. Scheinbar nutzt er auch die NPU, nur anstelle einer Antwort gibt er mir nur...

Hi there, I am back, the work was done, both, but the problem persist. In fact I have added a new LXC and a backup job for it and It was notified correctly. this is the content of /etc/pve/jobs.cfg just for learning intent because I think the best way to try and solve this is create a new job...

3.14 (S7) vmbr0 NAT + DHCP + /etc/hosts + interface cleanup (manual installation) 3.14.1 Required packages sudo su apt update apt install -y ipcalc dnsmasq 3.14.2 Enter vmbr0 parameters (IP/CIDR, DHCP, DNS) echo "Example vmbr0: 192.168.200.254/24" read -rp "IP/CIDR address for...

...+ grub-btrfs (GRUB menu) Network one "WAN" interface (external network) a vmbr0 bridge without physical interface (NAT + DHCP via dnsmasq) for VM/LXC Boot optimization: reduced NetworkManager-wait-online delay (5 seconds) Why "persistent" subvolumes in addition to the snapshotable root...

...SKIP: No RBD storage configured. = VIRTUAL GUEST CHECKS = SKIP: Skipping check for running guests - already upgraded. INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded.. PASS: systems seems to be upgraded and LXCFS is running with FUSE 3 library INFO: Checking for...

...SKIP: No RBD storage configured. = VIRTUAL GUEST CHECKS = SKIP: Skipping check for running guests - already upgraded. INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded.. PASS: systems seems to be upgraded and LXCFS is running with FUSE 3 library INFO: Checking for...

...6.0.5 libpve-network-perl: 1.2.4 libpve-rs-perl: 0.11.4 libpve-storage-perl: 9.1.0 libspice-server1: 0.15.2-1+b1 lvm2: 2.03.31-2+pmx1 lxc-pve: 6.0.5-3 lxcfs: 6.0.4-pve1 novnc-pve: 1.6.0-3 proxmox-backup-client: 4.1.1-1 proxmox-backup-file-restore: 4.1.1-1 proxmox-backup-restore-image: 1.0.0...

My issue was that I had upgrade the driver on the host, which worked perfectly fine, but when I was creating the lxc I was installing an old driver which was creating a driver mismatch, what I did is not install the driver on the lxc and then the lxc used the driver from the host as that was the...