Search results for query: lxc

From the API-viewer: It also states there that the newid is a required parameter.

Hello, I created a new user, added them to a new group, created a new resource pool, added an LXC to that resource pool, and then gave the new group the PVETemplateUser role in that resource pool. I then created an API key for the new user (without privilege separation, such that the key would...

...Proxmox leverages the Ubuntu kernel, enhanced with custom compile flags, built-in ZFS support, and patches optimized for virtual machines and LXC containers. (If you are curious of the patches, checkout the proxmox-kernel git.) Ubuntu 26.04 Release Information Final Planned Release Date...

Did you found a solution for this issue? I successfully passed through, Drivers is detected by TVH but its not scanning any channels as it should

...addition to an onboard 1GbE NIC) • pfSense VM (VM 200) on Proxmox • 1Gbps unmanaged switch for physical LAN clients • Mix of LXC containers and VMs on the same Proxmox host Current Network Config /etc/network/interfaces: auto lo iface lo inet loopback iface nic1 inet...

So still the same physical network? Yes, the timeout for checking the mount directory is 2 seconds. Telling from the error message, this is the command that fails for you and since you see the issue sporadically/randomly it might be related to the network after all.

Auf einem der Cluster-Nodes beobachte ich folgendes im Log: Apr 14 10:12:46 proxmox3 dbus-daemon[3026]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.457' (uid=33 pid=136911 comm="timedatectl show...

Hello. I'm now experiencing freezes which started three days ago and happens every day but in random time. Hardware is Hetzner Server Symptoms: Proxmox interface shows high IO delay, about 30-50%, while no significant IO operations are happening. I watched iotop, and 15M/s write was maximum...

Were you ever able to fix this? I'm having the same exact issue trying to map subdomains for other LXC's from a NPM LXC

1. ZFS in proxmox 2. I have ZFS folder mountpoints into LXC and docker runs in the LXC

Ok, das habe ich jetzt auf "statisch" geändert. Seitdem steht in der /etc/hosts natürlich die feste IP -- und der pmg8to9 Test läuft tatsächlich durch. Super -- besten Dank!

...dass DHCP unterstützt wird (dann müsste aber die tatsächliche IP per DNS auflösbar sein). Wenn es leicht möglich ist würde ich die IP in der LXC config hinterlegen, dann klappt auch der pmg8to9 test - ansonsten, sollte es auch so gehen (das Warning in dem Fall ignorieren). Ich hoffe das hilft.

Ja, genauso ist es auch: PMG läuft als LXC-Container und die IP kommt in dem VLAN über DHCP (die auf der OPNSense aber fest eingestellt ist) ... das funktionierte bisher. Sollte man es besser anders machen?

Wie wurde PMG installiert? - sieht auf den ersten blick nach einem LXC guest auf PVE aus? bekommt die VM die IP via DHCP?

If I make the container Privileged - the mount works but immich breaks and can't go to site through URL

.../Pictures umount: /Pictures: not mounted. mount: /Pictures: can't find in /etc/fstab. but when I do the mount command - this shows up (under LXC) 192.168.30.11:/Media/Pictures on /Pictures type nfs4...

I have an odd variation here - running an Immich LXC created from Proxmox VE Scripts - using this post guide, mounted a QNAP exported NFS share successfully and also mounted in LXC without issue using the mp0 entry Now where I try the same with an OpenMediaVault NFS export - the Proxmox node...

...And if you install https://github.com/MacRimi/ProxMenux on the host, that also provides a menu-driven walkthrough of bind mounting a network share inside the LXC container. In that case you must first create the mount of the share on the host system, and then create the bind mount in the LXC.

...and PVE nodes loads and network throughputs and latency are ok and with the same values as always. The backup job doesn't fail on the same vm/lxc, and it fails not regarding to the vm size, threfore we tought at first it was a network issue, but metrics are really good. From the source code...

...6.0.5 libpve-network-perl: 1.2.5 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-4 lxcfs: 6.0.4-pve1 novnc-pve: 1.6.0-3 proxmox-backup-client: 4.1.2-1 proxmox-backup-file-restore: 4.1.2-1 proxmox-backup-restore-image: 1.0.0...