Search results for query: lxc

...versus ifupdown2? What are you trying to achieve? If everything works for you you don't need to change anything. If however you have some network issues like the one described earlier in the thread it would make sense to change the lxc installed from the old template to match the newer one.

You can move back to the prior kernel (and keep on kernel 6.x) by doing this (this is from memory though, so be careful with it): 1. Create the APT preferences file (/etc/apt/preferences.d/proxmox-default-kernel) which instructs apt to keep on the 6x series kernel: Package...

I have LXCs from using standard proxmox templates: debian-13-standard_13.1-1_amd64.tar.zst and debian-13-standard_13.1-2_amd64.tar.zst. Based on output from `apt list --installed | cat`, I see: debian-13-standard_13.1-1_amd64.tar.zst LXC has: ifupdown/stable,now 0.8.44+deb13u1 amd64 [installed]...

...1.3.0 libpve-notify-perl: 9.1.2 libpve-rs-perl: 0.13.0 libpve-storage-perl: 9.1.2 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-4 proxmox-backup-client: 4.2.0-1 proxmox-backup-file-restore: 4.2.0-1 proxmox-backup-restore-image: 1.0.0...

...new. I tried to install nginx and did some other cleanup of my PVE and found that I can no longer use the default (xterm.js?) console with my LXCs from the PVE web GUI. However, using NoVNC does work (see first image - shows Connection failed for default console and NoVNC working in a...

Since the update to kernel 7.0.0-3, my VMs that used ppp do not work anymore in LXC containers (privileged). I was using openfortinet and since upgrade I get: ``` Couldn't set tty to PPP discipline: Operation not permitted ERROR: read: Input/output error ``` Tried both with adding capabilities...

...tar implementation would require modifications to our Rust code. As a workaround for now you could try converting the OCI image into an LXC template: skopeo copy docker://docker.io/freeipa/freeipa-server:fedora-44 oci:/tmp/freeipa-server:fedora-44 umoci unpack --image...

...you're good. Check with: bash ls -la /dev/kfd /dev/dri/ If those devices exist, skip the DKMS step on the host and go straight to the LXC setup using --no-dkms: bash # Inside the LXC container only: amdgpu-install -y --usecase=rocm --no-dkms The container doesn't need DKMS at all — it just...

Hi everyone! I need to get user_xattr as a mount option on my LXC container with Samba, currently I have ACLs activated, but I see only this when I fetch the attributes: root@fileserver /srv/storage# findmnt /srv/storage TARGET SOURCE FSTYPE OPTIONS /srv/storage /dev/rbd2 ext4...

Moin, und wie immer gilt: nur wenn man es selber macht, hat man etwas gelernt. Sonst versucht man sich an einem Serverbetriebssystem ohne das passende wissen und versucht hier irgendeine Funktion herauszupressen! Also gib dir mal ein Jahr und nutze ZFS als Basis.

Late to the party but all I did was: + Edit '/etc/pve/lxc/***.conf' + Change 'protection: *' to '0' + Then 'pct destroy *** --force'

...konnte HomeAssistant problemlos installiert und zum laufen gebracht werden. Yeah! (VLAN 3) Mit diesem Motivationsschub wollte ich Immich (als LXC) testen. Das HelperScript lief durch, aber der Container hat keine IP-Adresse von meiner DreamMachine bekommen. Geht das grundsätzlich nicht, wenn...

Incus und ProxmoxVE are both basically built around qemu/kvm for vms and lxc for containers. So I would expect that both have similiar capibalities, in fact nested virtualization and containers work on both with similiar caveats ( nested containers work best for lxc, for podman or docker they...

Read it on a blog and couldn't see how this was possible so had to ask. Thanks. Looks like running LXC in a nested hypervisor will be performant enough for my requirements.

...sorry. On all of my PVEs the host handles (local) storage, exclusively. In my Homelab the largest storage (in the cluster) is served by an LXC container (not: VM) to some clients. The host owns the storage and backup and management is handled there. ( --> "mount-points".) Technically you...

...other links errors across layers): TASK ERROR: unable to create CT 100 - Error while extracting OCI image: IO error: failed to unpack `/var/lib/lxc/100/rootfs/data-template/.configfiles/etc/krb5.conf.d/crypto-policies`: IO error: failed to unpack...

...32-core CPU (ROME) server with 384 GB RAM and fast SSDs in LVM-thin configuration. The original idea was to run Incus inside Proxmox VMs to host LXC guests. However, I read somewhere that Proxmox has special capabilities for nesting itself with VM and LXC guests. Wondering if Proxmox...

...with crane i now have this error: TASK ERROR: unable to create CT 100 - Error while extracting OCI image: IO error: failed to unpack `/var/lib/lxc/100/rootfs/data-template/.configfiles/etc/krb5.conf.d/crypto-policies`: IO error: failed to unpack...

Okay, hab meinen Fehler gefunden. Es gab ein LXC auf einer anderen physischen Proxmox-Maschine mit derselben IP-Adresse wie mein PBS, allerdings lauschte dieses LXC an einem anderen Port. Ich habe das korrigiert und nun läuft das BPS-GUI und auch das Login per Putty wieder. Ich bedanke mich...

What file system are you using for the Proxmox VE host root? As the error here is that the initrd could not find the actual root FS to continue booting. And how are the disks attached to the system, through some HBA, sata/nvme directly, ...? And while this might be kernel specific regression...