Login

Recent searches

No recent searches

Search options

Only available when logged in.
social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

485
active users

social.coop: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#proxmox

34 posts30 participants6 posts today
James M. Woodward<p>Okay <a href="https://infosec.exchange/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Proxmox</span></a>, what the crap. </p><p>This is an idiotic <a href="https://infosec.exchange/tags/darkmode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>darkmode</span></a>/#nightmode toggle. </p><p>I appreciate you offering it but it's just switching which elements are dark and which are light, of which your website has both.</p>
Radio Azureus<p><span class="h-card" translate="no"><a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>nixCraft</span></a></span> </p><p>One of the hashtags _guru</p><p><a href="https://mastodon.social/tags/bash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bash</span></a> <a href="https://mastodon.social/tags/csh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>csh</span></a> <a href="https://mastodon.social/tags/ksh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ksh</span></a> <a href="https://mastodon.social/tags/sh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sh</span></a> <a href="https://mastodon.social/tags/parameters" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>parameters</span></a> &nbsp;&nbsp;<a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.social/tags/XEN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>XEN</span></a> <a href="https://mastodon.social/tags/VM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VM</span></a> <a href="https://mastodon.social/tags/Boot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Boot</span></a> <a href="https://mastodon.social/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Proxmox</span></a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programming</span></a>&nbsp;&nbsp;<a href="https://mastodon.social/tags/POSIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>POSIX</span></a></p>
cyber4EDU e.V.<p>ℹ️ Für alle <a href="https://digitalcourage.social/tags/Interessierten" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Interessierten</span></a> an <a href="https://digitalcourage.social/tags/DigitalerBildung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DigitalerBildung</span></a> :</p><p>📅 Am morgigen Mittwoch, 16.04.2025 ist wieder unser Großgruppentreffen. <br>Mit vorangehender Einführungsrunde für alle Neuen bzw. Interessierten.<br>🕣 Die Einführungsrunde startet um 20:30 Uhr in diesem BBB:<br><a href="https://bbb.cyber4edu.org/b/chr-tb0-hgo-yne" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">bbb.cyber4edu.org/b/chr-tb0-hg</span><span class="invisible">o-yne</span></a><br>Dort werden alle Neuen von MoniKa und pnrd in Empfang genommen, bekommen erste Infos zu unserer Arbeit und können Fragen stellen. </p><p>💬 Danach wechseln wir zu 21:00 Uhr in die Großgruppe.<br>Dort starten wir mit den wichtigten Infos vom Vorstand, den AGs und widmen uns dann einem aktuellen Thema. <br>⁉️ Das Thema diese Woche: Wir haben einen Gast: Mario erzählt uns was zu <a href="https://digitalcourage.social/tags/ProxMox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ProxMox</span></a> und <a href="https://digitalcourage.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> an Schulen<br>Fokus: Was können Schulen und Schulträger selber tun?</p><p>Basis/Vorbereitung: <br>👂 Podcast FOCUS ON: Linux: Linux im Schulwesen<br>* Webseite der Episode: <a href="https://focusonlinux.podigee.io/119-linux-im-schulwesen" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">focusonlinux.podigee.io/119-li</span><span class="invisible">nux-im-schulwesen</span></a></p><p>Wenn euch das interessiert, kommt vorbei und tauscht euch mit uns aus. 💻 20:30 geht's los!<br><a href="https://digitalcourage.social/tags/cyberLZ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cyberLZ</span></a> <a href="https://digitalcourage.social/tags/FediLZ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FediLZ</span></a> <a href="https://digitalcourage.social/tags/Bildung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Bildung</span></a> <a href="https://digitalcourage.social/tags/Schule" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Schule</span></a> <a href="https://digitalcourage.social/tags/schul_it" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>schul_it</span></a> <a href="https://digitalcourage.social/tags/Schul" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Schul</span></a>-IT</p>
stdevel<p><span class="h-card" translate="no"><a href="https://techhub.social/@estevez" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>estevez</span></a></span> Wow, that looks awesome. Perfect for my next NAS or <a href="https://chaos.social/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Proxmox</span></a> build.</p>
Yehor 🇺🇦<p>I want a 12-16 cores node for my <a href="https://techhub.social/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Proxmox</span></a> cluster. Like a real production node for high loads. I also found a perfect case for it, it’s <a href="https://techhub.social/tags/Jonsbo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Jonsbo</span></a> N1. Looks like I’m on the way of building myself a PC first time in 20 years.</p><p><a href="https://techhub.social/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelab</span></a> <a href="https://techhub.social/tags/HomeServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HomeServer</span></a> <a href="https://techhub.social/tags/pcbuild" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pcbuild</span></a> <a href="https://techhub.social/tags/pcbuilding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pcbuilding</span></a></p>
Mika<p>I have finally caved in and dove into the rabbit hole of <a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> Container (<a href="https://sakurajima.social/tags/LXC" rel="nofollow noopener noreferrer" target="_blank">#LXC</a>) on <a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener noreferrer" target="_blank">#Proxmox</a><span> 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.<br><br>I now have a </span><a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener noreferrer" target="_blank">#Jellyfin</a> and <a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener noreferrer" target="_blank">#ErsatzTV</a> setup running on LXCs with working iGPU passthrough of my server's <a href="https://sakurajima.social/tags/AMD" rel="nofollow noopener noreferrer" target="_blank">#AMD</a> Ryzen 5600G APU. My <a href="https://sakurajima.social/tags/Intel" rel="nofollow noopener noreferrer" target="_blank">#Intel</a> <a href="https://sakurajima.social/tags/ArcA380" rel="nofollow noopener noreferrer" target="_blank">#ArcA380</a> 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 <a href="https://sakurajima.social/tags/Kubernetes" rel="nofollow noopener noreferrer" target="_blank">#Kubernetes</a>, <a href="https://sakurajima.social/tags/RKE2" rel="nofollow noopener noreferrer" target="_blank">#RKE2</a><span> cluster on LXC nodes instead of VMs - and if that's viable or perhaps better.<br><br>Anyway, I've updated my </span><a href="https://sakurajima.social/tags/Homelab" rel="nofollow noopener noreferrer" target="_blank">#Homelab</a> Wiki with guides pertaining LXCs, including creating one, passing through a GPU to multiple unprivileged LXCs, and adding an <a href="https://sakurajima.social/tags/SMB" rel="nofollow noopener noreferrer" target="_blank">#SMB</a><span> share for the entire cluster and mounting them, also, on unprivileged LXC containers.<br><br></span>🔗 <a href="https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/proxmox.md#linux-containers-lxc" rel="nofollow noopener noreferrer" target="_blank">https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/proxmox.md#linux-containers-lxc</a></p>
Mika<p>Wow, there's a 9-year 'bug' on <a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener noreferrer" target="_blank">#Proxmox</a> whereby disabling a (SMB/CIFS) storage on the cluster, does not unmount the storage automatically until a complete reboot (of all nodes)... which doesn't seem ideal in a <a href="https://sakurajima.social/tags/homelab" rel="nofollow noopener noreferrer" target="_blank">#homelab</a><span> setting - and there doesn't seem to be a command of sort that could do this manual unmount of disabled storage either, cluster-wide.<br><br></span>🔗 <a href="https://bugzilla.proxmox.com/show_bug.cgi?id=1016" rel="nofollow noopener noreferrer" target="_blank">https://bugzilla.proxmox.com/show_bug.cgi?id=1016</a><span><br><br></span>🔗 <a href="https://forum.proxmox.com/threads/pvesm-umount.115269" rel="nofollow noopener noreferrer" target="_blank">https://forum.proxmox.com/threads/pvesm-umount.115269</a><span><br><br></span>🔗 <a href="https://forum.proxmox.com/threads/cifs-disable-does-not-unmount-causing-flood-of-errors-in-syslog.125610" rel="nofollow noopener noreferrer" target="_blank">https://forum.proxmox.com/threads/cifs-disable-does-not-unmount-causing-flood-of-errors-in-syslog.125610</a></p>
OS-SCI<p>During <a href="https://mastodon.social/tags/FossFEST" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FossFEST</span></a> Ronald Otto CEO of Tuxis gave a <a href="https://mastodon.social/tags/Masterclass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Masterclass</span></a> about <a href="https://mastodon.social/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Proxmox</span></a>, open source virtualisation. Check out the full video:&nbsp;<a href="https://www.youtube.com/watch?v=akHHWNf_5RE&amp;t=130s&amp;ab_channel=OS-SCi&nbsp;" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=akHHWNf_5R</span><span class="invisible">E&amp;t=130s&amp;ab_channel=OS-SCi&nbsp;</span></a></p>
Armbian Linux<p>🚀 Introducing Armbian Cloud Images – optimized for x86 &amp; aarch64 cloud deployments!</p><p> ✅ Lightweight &amp; Ultra-fast boot<br> ✅ Pre-enabled <a href="https://fosstodon.org/tags/Docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Docker</span></a><br> ✅ ZRAM memory boost<br> ✅ armbian-config for easy setup</p><p>Build your own branded cloud OS today!<br> 🔗 <a href="https://www.armbian.com/newsflash/armbian-cloud-images/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">armbian.com/newsflash/armbian-</span><span class="invisible">cloud-images/</span></a></p><p><a href="https://fosstodon.org/tags/Armbian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Armbian</span></a> <a href="https://fosstodon.org/tags/netcup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>netcup</span></a> <a href="https://fosstodon.org/tags/Hetzner" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Hetzner</span></a> <a href="https://fosstodon.org/tags/CloudComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CloudComputing</span></a> <a href="https://fosstodon.org/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DevOps</span></a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://fosstodon.org/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Proxmox</span></a> <a href="https://fosstodon.org/tags/QEMU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>QEMU</span></a></p>
gyptazy<p>Wow - Beam Networks made a YT review about my <a href="https://mastodon.gyptazy.com/tags/ProxLB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ProxLB</span></a> project for <a href="https://mastodon.gyptazy.com/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Proxmox</span></a>!</p><p>ProxLB brings in some more features known from VMware like DRS etc. and it’s fully <a href="https://mastodon.gyptazy.com/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a>. You can find more information in the YouTube review - really appreciated - thanks!</p><p><a href="https://m.youtube.com/watch?v=uh7RdgpjRCM" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">m.youtube.com/watch?v=uh7Rdgpj</span><span class="invisible">RCM</span></a></p>
Mika<p>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 <a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener noreferrer" target="_blank">#Jellyfin</a>'s <code>xml</code> configs for any wrong/old paths/values, and lastly, the <a href="https://sakurajima.social/tags/SQLite" rel="nofollow noopener noreferrer" target="_blank">#SQLite</a> DBs themselves which had old paths as well - most of which were easy to fix as they're <code>text</code> values, but some were (JSON) <code>blob</code>s, using the same extension on <a href="https://sakurajima.social/tags/VSCode" rel="nofollow noopener noreferrer" target="_blank">#VSCode</a><span>, 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.<br><br>Now my Jellyfin </span><a href="https://sakurajima.social/tags/LinuxServer" rel="nofollow noopener noreferrer" target="_blank">#LinuxServer</a>.io container sitting in an unprivileged (<a href="https://sakurajima.social/tags/Debian" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> <a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>) <a href="https://sakurajima.social/tags/LXC" rel="nofollow noopener noreferrer" target="_blank">#LXC</a> container on <a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener noreferrer" target="_blank">#Proxmox</a> is set up with hardware transcoding using the <a href="https://sakurajima.social/tags/AMD" rel="nofollow noopener noreferrer" target="_blank">#AMD</a> Ryzen 5 5600G onboard iGPU (cos I'm getting impatient in waiting for my <a href="https://sakurajima.social/tags/Intel" rel="nofollow noopener noreferrer" target="_blank">#Intel</a> <a href="https://sakurajima.social/tags/ArcA380" rel="nofollow noopener noreferrer" target="_blank">#ArcA380</a> to arrive). I'll update my <a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener noreferrer" target="_blank">#ErsatzTV</a> 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 <a href="https://sakurajima.social/tags/Plex" rel="nofollow noopener noreferrer" target="_blank">#Plex</a><span>) 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.<br><br>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.<br><br></span>🔗 <a href="https://github.com/jellyfin/jellyfin-web/issues/4346" rel="nofollow noopener noreferrer" target="_blank">https://github.com/jellyfin/jellyfin-web/issues/4346</a><span><br><br></span>🔗 <a href="https://github.com/jellyfin/jellyfin/issues/13858" rel="nofollow noopener noreferrer" target="_blank">https://github.com/jellyfin/jellyfin/issues/13858</a><span><br><br>RE: </span><a href="https://sakurajima.social/notes/a6j9bhrbtq" rel="nofollow noopener noreferrer" target="_blank">https://sakurajima.social/notes/a6j9bhrbtq</a></p>
Neil Brown<p>New blogpost: <strong>"Trialling a move from a NUC to a container"</strong></p><p>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.</p><p>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.</p><p><a href="https://neilzone.co.uk/2025/04/trialling-a-move-from-a-nuc-to-a-container/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">neilzone.co.uk/2025/04/trialli</span><span class="invisible">ng-a-move-from-a-nuc-to-a-container/</span></a></p><p><a href="https://mastodon.neilzone.co.uk/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FOSS</span></a> <a href="https://mastodon.neilzone.co.uk/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.neilzone.co.uk/tags/proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proxmox</span></a> <a href="https://mastodon.neilzone.co.uk/tags/SmallWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SmallWeb</span></a></p>
Michael<p>Lastly, I have <a href="https://mastodon.social/tags/immich" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>immich</span></a> in a <a href="https://mastodon.social/tags/proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proxmox</span></a> VM as a readonly viewer of the samba share so I can see photos on my phone and other devices. My devices connect to <a href="https://mastodon.social/tags/wireguard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>wireguard</span></a> when out of the house so they can still access the server to sync!</p><p>Hope that is helpful to someone, and let me know what I'm doing wrong and can improve!</p><p>🧵 4/4</p>
Michael<p>Next I run <a href="https://mastodon.social/tags/syncthing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>syncthing</span></a> on my laptop, and on my <a href="https://mastodon.social/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelab</span></a> <a href="https://mastodon.social/tags/intelN100" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>intelN100</span></a> <a href="https://mastodon.social/tags/n100" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>n100</span></a> mini pc / server that runs in the cupboard and is very <a href="https://mastodon.social/tags/lowpower" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>lowpower</span></a> I run <a href="https://mastodon.social/tags/proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proxmox</span></a> and this also has a <a href="https://mastodon.social/tags/samba" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>samba</span></a> share which allows any other network devices to see the media.</p><p>With syncthing running, I always have two copies of the media, but for backup I was using <a href="https://mastodon.social/tags/rclone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rclone</span></a> to send an encrypted copy to <a href="https://mastodon.social/tags/googledrive" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>googledrive</span></a> - which I am in the process of switching over to <a href="https://mastodon.social/tags/nextcloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nextcloud</span></a> running on <a href="https://mastodon.social/tags/hetzner" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hetzner</span></a></p><p>🧵 3/4</p>
Jan ☕🎼🎹☁️🏋️‍♂️<p>Been testing out the <a href="https://fedi.kcore.org/tags/virtiofs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>virtiofs</span></a> support now baked into <a href="https://fedi.kcore.org/tags/proxmoxVE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proxmoxVE</span></a>. It works, had to do some <a href="https://fedi.kcore.org/tags/selinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>selinux</span></a> adjustments on <a href="https://fedi.kcore.org/tags/fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fedora</span></a> to allow my <a href="https://fedi.kcore.org/tags/podman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>podman</span></a> containers to use the mountpoint. Added this policy</p><p>```<br>(allow container_t unlabeled_t ( dir ( read write )))<br>```</p><p>In raw speed it is definitely not a winner - <a href="https://fedi.kcore.org/tags/nfs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nfs</span></a> 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.</p><p><a href="https://fedi.kcore.org/tags/proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proxmox</span></a></p>
Mika<p>Bruh, I might've wasted my time learning how to passthrough a GPU to an <a href="https://sakurajima.social/tags/LXC" rel="nofollow noopener noreferrer" target="_blank">#LXC</a> container on <a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener noreferrer" target="_blank">#Proxmox</a> (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 <i>magic</i> <a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <i>fu</i><span> 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.<br><br>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 </span><a href="https://sakurajima.social/tags/AMD" rel="nofollow noopener noreferrer" target="_blank">#AMD</a> iGPU (until my <a href="https://sakurajima.social/tags/Intel" rel="nofollow noopener noreferrer" target="_blank">#Intel</a> <a href="https://sakurajima.social/tags/ArcA380" rel="nofollow noopener noreferrer" target="_blank">#ArcA380</a> GPU arrives) and see if the root user + service user on the container could access it/use it for transcoding on <a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener noreferrer" target="_blank">#Jellyfin</a>/<a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener noreferrer" target="_blank">#ErsatzTV</a>, and 2) Add a SMB/CIFS storage on the Proxmox Datacenter, tho my <a href="https://sakurajima.social/tags/NAS" rel="nofollow noopener noreferrer" target="_blank">#NAS</a><span> 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.<br><br></span><a href="https://sakurajima.social/tags/Homelab" rel="nofollow noopener noreferrer" target="_blank">#Homelab</a> folks who have done this, feel free to give some tips or wtv if you've done this before!</p>
Public *
Mika

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

ExploreLive feeds
About