Super simple, like 30 minutes to setup mergerfs and then the bind mounts are a few lines added to the LXC config files at most. This isn’t necessarily needed, but I have users setup on the proxmox host with access to specific directories that are kind of a pain in the ass to remap the LXC users to, but were needed to give my *arr stack access to everything needed without giving access to the entire storage pool. Hard links won’t work across multiple bind mounts because the container will see them as separate file systems, so if your setup is /mnt/storage/TV, /mnt/storage/downloads, etc. then you’d have to pass just /mnt/storage as the bind mount.

On the other hand, I’ve been mounting my storage drives on the proxmox host with mergerfs and exposing what I need to the LXCs with bind mounts for years, and I haven’t had a single issue with it across multiple major version upgrades.

You can pass the storage you need to the LXCs with bind mounts. No network connection needed.

https://github.com/gtxaspec/wz_mini_hacks adds wireguard and other features to a few supported Wyze cameras. I haven’t tried wireguard because mine is on my home network but it works great for streaming rtsp locally.

Bitwarden caches your vault to your device, so you don’t actually need a live connection to the server.

RADV has the least issues but I still tend to test AMDVLK (vulkan-headers makes switching drivers per-game easy) for any big performance differences, and it’s typically the first thing I try for crashes now. If you want to use ray tracing at all you should definitely use AMDVLK, it performs way better.

It ranges from significant performance differences between the drivers with specific games to games having rendering issues with specific drivers. A lot of games don’t work at all with the proprietary driver.

My most recent issue was with the Indiana Jones game having horrible traversal stuttering making some areas basically unplayable on RADV, but AMDVLK had no stuttering and better framerate overall.

I’m not using an immutable distro and the issues with the Vulkan drivers have nothing to do with them.

AMD is just simpler because you don’t have to manage the drivers, but it’s really not a big deal. It’s very easily handled.

Honestly this isn’t as true as I was led to believe it was before I switched to AMD. Just like Nvidia has issues between the proprietary driver and nouveau; AMD has its own mix of issues with Vulkan between RADV (mesa), AMDVLK, and AMD’s proprietary driver on a per-game basis at times.

I tried fish before switching to zsh because it has much better compatibility with bash, and I think bash/zsh handles a lot of things like aliases way better. I’m also on CachyOS and the default zsh config with ohmyzsh and powerline10k it comes with is great.

What you’re describing sounds pretty much exactly like how I use Proxmox at this point (everything in LXCs, most just running docker on Alpine) and I’ve been wanting to make the switch to Incus for a while. Did you migrate your LXCs over from Proxmox? I’m a little worried about how painful that process might be.

That reddit thread is horrible advice, it’s just mapping the LXC root user to the host root user, which is just a privileged LXC with extra steps (and maybe less secure).

The reason you’re probably having issues is that your root user in the LXC is mapped to the host user 100000 by default, and that user doesn’t have access to the share, but you can change that with mount options or creating a user with 100000:100000 and adding it to a group with access.

Gnome is very functional, it’s just meant to function one very specific way.

I use Tautulli, but I’m not sure if that is going to cover all the same use cases.

For anything. You can get a push notification for anything you can make run a script or send an http request.

Me too. I recently switched from an RTX 2080 to a 7900 XTX, which is way more powerful for games, but local LLM performance tanked without CUDA.

Just run docker in an LXC. That’s what I do when I have to.

I’m not really worried about it. Each LXC runs as its own user on the host, and they only have access to what they need to run each service.

If there’s an exploit found that makes that setup inherently vulnerable then a lot of people would be way more screwed than I would.

I don’t have anything publically accesible on my network (other than wireguard), but if I did I’d just put whatever it was on its own VLAN, run a wireguard server on it, and use a VPS as a reverse proxy that connects to it.

I only use unprivileged LXCs and everything I host on my network runs in its own LXC, so I’m not really worried about someone getting access to the host from there.

I occasionally get this same thing, or it’ll render one frame of SDDM and then freeze on that frame, and I’ve also never been able to fix it. I’m on CachyOS with an RTX 2080.

I just bought a 7900 XTX that I’m waiting to be shipped, so I wonder if it’ll go away with an AMD GPU.

Edit: Hasn’t happened once with the AMD card, and another frequent issue I had with Vulkan was fixed too. I’m blaming nvidia.