I really feel like #Incus will be eating #Proxmox' lunch within a few years. Between the webUI, the clustering features and the in-development custom #Debian-based secure Incus OS, there's all that's needed for a reboot on saner primitives of the #container and #virtualization host.

https://discuss.linuxcontainers.org/t/incus-6-7-has-been-released/22099
https://stgraber.org/2025/01/04/incus-in-2024-and-beyond/
https://github.com/lxc/incus-os

Heute auf meinem #DellWyse5070 #Proxmox installiert und direkt nen #LXC-Container mit #AdGuardHome gestartet .
Netz jetzt: werbefrei , schnell und unter voller Kontrolle – nie wieder ohne!

Mit bisschen Internet & Hilfe von #ChatGPT in unter 1h erledigt.

New blogpost: "Trialling a move from a NUC to a container"

I spent some time today setting up a container to run my webserver and related tools (including mkdocs and hugo), as a test replacement for the current Intel NUC.

A current unknown - nothing like testing in production :) - is how well this small container will stand up to a lot of fedi-originated traffic. This is that test.

https://neilzone.co.uk/2025/04/trialling-a-move-from-a-nuc-to-a-container/

Been testing out the #virtiofs support now baked into #proxmoxVE. It works, had to do some #selinux adjustments on #fedora to allow my #podman containers to use the mountpoint. Added this policy

```
(allow container_t unlabeled_t ( dir ( read write )))
```

In raw speed it is definitely not a winner - #nfs is easily double the speed. But on this particular VM I don't need the speed - it is nice that this is all self-contained now, and I can actually remove NFS altogether.

Bruh, I might've wasted my time learning how to passthrough a GPU to an #LXC container on #Proxmox (as well as mount a SMB/CIFS share) and write up a guide (haven't been able to test yet, cept with the latter) - all by doing some seemingly magic #Linux fu with some user/group mappings and custom configs, if it turns out that you could actually achieve the same result just as easily graphically using a standard wizard on PVE.

It's 4am, I'll prolly try to find time later during the day, or rather evening (open house to attend at noon), and try using the wizard to 1) Add a device passthrough on an LXC container for my #AMD iGPU (until my #Intel #ArcA380 GPU arrives) and see if the root user + service user on the container could access it/use it for transcoding on #Jellyfin/#ErsatzTV, and 2) Add a SMB/CIFS storage on the Proxmox Datacenter, tho my #NAS is also just a Proxmox VM in the same cluster (not sure if this is a bad idea?) and see if I could mount that storage to the LXC container that way.

#Homelab folks who have done this, feel free to give some tips or wtv if you've done this before!

So that #proxmox 6.14 kernel is not a good idea when doing gpu passthrough atm...

https://forum.proxmox.com/threads/opt-in-linux-6-14-kernel-for-proxmox-ve-8-available-on-test-no-subscription.164497/post-763113

I'll just have to wait to see idle power wattage drop

#ProxmoxBackupServer 3.4 has been released (#Proxmox / #ProxmoxBS / #BackupServer / #ZFS / #OpenZFS / #Linux / #Debian / #Bookworm / #DebianBookworm) https://proxmox.com/

#ProxmoxVE 8.4 has been released (#Proxmox / #VirtualEnvironment / #Virtualization / #VirtualMachine / #VM / #Linux / #Debian / #Bookworm / #DebianBookworm / #QEMU / #LXC / #KVM / #ZFS / #OpenZFS / #Ceph) https://proxmox.com/

Seems like Snowflake proxy v2.11.0 uses more RAM, about 100 - 200 MB. This used to be around 20 - 50 MB.

Still have enough RAM on my Proxmox server to dedicate for this VM though so I now dedicate from 3 GB to 4 GB RAM since I run 20 snowflake proxy process on this VM.

I'm gonna check back later and see if it uses up all that 4 GB.

I use Fedora, btw.

Du willst Home Assistant installieren und dein Smart Home selbst verwalten? Dann bist du hier genau richtig. Ich zeige dir, wie du es auf Proxmox einrichtest. Neugierig geworden? Jetzt direkt weiterlesen: https://hobbyblogging.de/home-assistant-installieren #SmartHome #HomeAssistant #Proxmox #Automation #Technik

Heute das erste Mal #Proxmox installiert - geiler Scheiss

I'm writing a guide on splitting a GPU passthrough across multiple #Proxmox #LXC containers based on a few resources, including the amazing Jim's Garage video.

Does anyone know the answer to this question of mine though, on why he might've chosen to map a seemingly arbitrary GID 107 on the LXC Container to the Proxmox host's render group GID of 104 - instead of mapping 104 -> 104, as he did with the video group, where he mapped 44 -> 44 (which seems to make sense to me)?

I've watched his video seemingly a million times, and referred to his incredibly simplified guide on his GitHub that's mostly only meant for copy-pasting purposes, and I couldn't quite understand why yet - I'm not sure if it really is arbitrary and 107 on the LXC Container could be anything, including 104 if we wanted to... or if it (i.e. 107) should've been the LXC Container's actual render group GID, in which case then it should've also been 104 instead of 107 on his Debian LXC Container as it is on mine.

Anyway, super excited to test this out once my #Intel #ArcA380 arrives. I could probably already test it by passing through one of my node's Ryzen 5 5600G iGPU, but I worry if I'd screw something up, seeing that it's the only graphics onboard the node.

https://github.com/JamesTurland/JimsGarage/issues/141

On en parle moins, et pourtant, il est essentiel pour mener un projet à bien, surtout quand il y a des pertes de données
Je parle de #Proxmox #Backup Server
Ce dernier passe en version 3.4
Avec ça...
Performances optimisées pour la collecte des déchets (purge/nettoyage) ;
Sélection d'instantanés de sauvegarde granulaire pour les tâches de synchronisation ;
Construction statique du client Proxmox Backup ;
Augmentation du débit pour la sauvegarde de bande ;
...

Has anyone had problems with #Proxmox GMBH not honoring subscription cancellations?

I love #Podman, but gosh is it needlessly complicated (to setup, correctly) compared to #Docker. I'll continue using it over Docker on my systems, but recommending/advocating to people's sake (when it comes to containerisation), maybe I'll stick with Docker.

If you're just setting it up on your personal machine, it's easy - some aspects may even be simpler than Docker - but the moment you start getting into things like getting it to work on a #Proxmox #LXC container... it gets messy real fast.