I have finally caved in and dove into the rabbit hole of #Linux Container (#LXC) on #Proxmox during my exploration on how to split a GPU across multiple servers and... I totally understand now seeing people's Proxmox setups that are made up exclusively of LXCs rather than VMs lol - it's just so pleasant to setup and use, and superficially at least, very efficient.

I now have a #Jellyfin and #ErsatzTV setup running on LXCs with working iGPU passthrough of my server's #AMD Ryzen 5600G APU. My #Intel #ArcA380 GPU has also arrived, but I'm prolly gonna hold off on adding that until I decide on which node should I add it to and schedule the shutdown, etc. In the future, I might even consider exploring (re)building a #Kubernetes, #RKE2 cluster on LXC nodes instead of VMs - and if that's viable or perhaps better.

Anyway, I've updated my #Homelab Wiki with guides pertaining LXCs, including creating one, passing through a GPU to multiple unprivileged LXCs, and adding an #SMB share for the entire cluster and mounting them, also, on unprivileged LXC containers.

https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/proxmox.md#linux-containers-lxc

I... actually managed to do this and it was somewhat messy to get through with it, but I did it. My 'stoppers' initially were simply needing to update some of the #Jellyfin's xml configs for any wrong/old paths/values, and lastly, the #SQLite DBs themselves which had old paths as well - most of which were easy to fix as they're text values, but some were (JSON) blobs, using the same extension on #VSCode, this wasn't that hard to do either by simply exporting the blob, editing the blob's JSON text value, and reimporting the blob to the column.

Now my Jellyfin #LinuxServer.io container sitting in an unprivileged (#Debian #Linux) #LXC container on #Proxmox is set up with hardware transcoding using the #AMD Ryzen 5 5600G onboard iGPU (cos I'm getting impatient in waiting for my #Intel #ArcA380 to arrive). I'll update my #ErsatzTV container to do the same. Everything's perfect now, 'cept, I still wouldn't recommend users to stream Jellyfin on the web or a web-based client using transcoding, cos while the transcoding itself is perfect, Jellyfin seems to have an issue (that I never got on #Plex) whereby the subtitle would desync pretty consistently if not direct playing - with external or embedded subs, regardless. Dk if that can ever be fixed though, considering the issue has been up since 2023 with no fix whatsoever.

There's also a separate issue I'm having where Jellyfin does not seem to support discovering/serving media files that are contained in a symlink directory (even though there were some people on their forums reporting in the past that it should) - I've reported it last week, but it's not going anywhere for now. Regardless though, I'm absolutely loving Jellyfin despite some of its rough edges, and my users are loving it too. I think I've considered myself 'migrated' from Plex to Jellyfin, but I'll still keep Plex around as backup for these 2 cases/issues I've mentioned, for now.

https://github.com/jellyfin/jellyfin-web/issues/4346

https://github.com/jellyfin/jellyfin/issues/13858

RE: https://sakurajima.social/notes/a6j9bhrbtq

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!

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

Was #listening earlier to the latest @FLOSS_Weekly talking about #Incus and #lxc for #linux containers, the latter being something I was interested in doing on my Fedora VM running in Bhyve. I've already installed Incus and will follow this tutorial to get familiar with it for now.

https://linuxcontainers.org/incus/docs/main/

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

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.

Pues nueva versión de #Proxmox: la 8.4. Basada en #Debian 12.10 "Bookworm" con el Linux kernel 6.8.12 y el kernel 6.14 opcionalmente, #QEMU 9.2.0, #LXC 6.0.0, #ZFS 2.2.7 con compatibilidad para kernel 6.14 y Ceph Squid 19.2.1. Para más cosicas interesantes que han añadido, se puede leer en: https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.4

Was sagt das über mich aus, dass ich #Debian #LXC Container in der Kommandozeile mittlerweile beim ersten Versuch ohne nachschauen erzeugen kann mit lxc-create? ​​

Heute neu dazugekommen: Ein Container namens "piped" ​​

The latest round of LTS updates for #Incus, #LXC and #LXCFS is now out!
https://stgraber.org/2025/04/04/lxc-lxcfs-incus-6-0-4-lts-release/

I'm at the absolute end of my comprehension of Wireguard and WG-Easy. I, for the love of anything, CANNOT get my VPN to stay connected for more than 3 minutes. I have tried connecting via direct Public IP, my Domain with A Certs, PersistentKeepalive, changing/removing UFW/Firewall, hosting on bare metal, LXC, VM. I am at a complete loss and simply do not understand this anymore. If anyone has any ideas, please send them my way. #proxmox #selfhosting #vpn #lxc #vm #wireguard

Hey networking/LXC specialists.

I have NextCloudPi running as an LXC container.

To access it, I set up routing on my Mikrotik router (screenshot).

The problem is that accessing NCP this way is very slow, I need to wait 5-10 seconds for the page to load.

I have Tailscale installed in the container, and accessing NCP using the Tailscale host name is nearly instantaneous.

What is the better approach:
- one service (eg. database + web app) per LXC container
- one container per group of services (eg. all web apps + databases)
?? And why?
#lxc #containers #askfedi

Ein Talk auf den #ChemnitzerLinuxTage über das Virtualisierungssystem was wir auch für unsere Mitglieder VMs verwenden.

#KVM #Qemu #LXC

https://ffmuc.media.ccc.de/events/clt/2025/h264-hd/clt25-81-deu-Incus_-_ein_System_Container_und_Virtual_Machine_Manager_hd.mp4

#clt2025 #clt25 @clt_news

Andere interessante Vorträge:
https://ffmuc.media.ccc.de/events/clt/2025/h264-hd/clt25-94-deu-Einfuehrung_in_nftables_hd.mp4
https://ffmuc.media.ccc.de/events/clt/2025/h264-hd/clt25-92-deu-Loadbalancer_mit_Kerneltools_-_mit_XDP_den_Kernel_erweitern_hd.mp4

No April Fools' joke - the new #ProxLB release is scheduled for the 1st of April! Stay tuned!

ProxLB is an advanced #loadbalancer for #Proxmox clusters that brings in features like #DRS (known from #VMware), #maintenance mode and (anti-)#affinity groups.

I just published a new Ansible role that automatically populates host variables with Proxmox-related information from the inventory. This includes node assignment, VM/container type, status, MAC address, QEMU agent status, and resource allocation. For now, it supports a single cluster.

Let me know if you have any feedback.

#ansible #proxmox #cluster #lxc #vm #devops #selfhosted #selfhosting #homelab

https://github.com/LucasJanin/ansible-role-proxmox-node-discovery

#HomeAssistant #SelfHosting
I have been using my HAOS instance to host many add-ons not related to HA.
Now spinning those off into separate instances, e.g. Vaultwarden, Uptime-Kuma.
Also, moved Zigbee2MQTT add-on into separate instance.
These moves are aimed at improving the performance of Home Assistant. So far so good.
Oh, 'instance' means separate #lxc or #incus containers or VM's.

LXD with Win11 no network adapter driver #drivers #lxc #lxd

https://askubuntu.com/q/1544000/612