From my short time with proxmox, I had to dive into the command line to do configuration at the host level that couldnt be done with the UI. I think nixos will help replacd those ad hoc configurations with nix options. In the many articles I read about gpu passthru, and also doing harddrive passthru, I had to work in the host debian environment.

I dumped proxmox because I couldnt get gpu passthrough to work, and havent looked back. Nixos modules and docker have served me better than VMs for my usecase.

Yes I’ve got that set but still running into issues at runtime.

It was not configured correctly. Its a nixos bug. Thanks for pointing out the daemon config its what lead me down to solving the docker problem.

Yes thats the nvidia-container-toolkit I described above. It should be installed.

As a community, I do think we get hungup on distros. Most of them, as you mentioned, are just different defaults of the same packages.

But at the maintainer level, I do think theres a lot of work distributions do at making sure the software they choose as defaults are up to date, secure, and work with one another. I dont enounter it often, but relying on maintainers to prevent mismatched depencies ending up in the day-to-day linux user has to be worth something. And every set of defaults needs that level of assurance, I would think. Im not a maintainer, I could be off here.

This is a very specific project. This is cool to see. Im curious if anybody else would use this.

You could always dip your toe into a tiling window manager instead of a desktop environment. Its got an initial learning curve, and it helps to have something to do to learn it, and not just playtesting it.

Wow, I never considered swap. I’ve had this problem with my laptop for the last year. I’ll fix this, thank you.

To be fair, you’re taking on a lot of new things at once. You can spin up docker containers on windows too, all while using a UI. I think it’s great your exposing yourself to self hosting, linux, command line interface, and containerization all at once, but don’t beat yourself up for it taking longer than expected. A lot of it takes time. I encourage you to keep trying and playing. Good luck!

Do you have recommendations for a new controller? I’ve been looking at 8bitdos: https://www.8bitdo.com/ultimate-2.4g-wireless-controller/

I think its best to move past bluetooth, if we can. I dont think it was ever a great protocol. But things like phones can’t always have dongles either, so it’s necessary.

Do you use a dock or bar? I find it hard to justify it these days. It tells me the time, thats about it.

Add this to your nix.conf: experimental-features = nix-command flakes

Then check out nix --help.

Here’s an example of a tutorial that uses flakes and the new cli. You might glance through here to see how the syntax compares: https://zero-to-nix.com/start

They have resolved this exact problem. There is an “experimental” cli tool that fixes a lot of your complaints about nix-env, nix-channel, etc. Itcs wrapped together with “flakes”. This newer feature is a little different, and working with or without flakes segments the community AND the types of articles about nix, like this one.

As far as I know though, nixos related thing still have a bizarre set of commands, and even with flakes “nixos-rebuild switch --upgrade” is still how you switch configs.

And as far as installation goes, using nix-env -iA really is a bad practice. Thats installing something ad hoc like you would in any other package manager. That defeats the point of nixos, where your configuration file explicitly defines all the packages you need installed, and nothing else. Nix will remove any packages you didnt specify.

Thanks for sharing these feature. I run pihole but knew nothing about this. As my move my implementation to new hardware I’ll definitely be adding this.

Can you elaborate on update system? AppImage is just a format, right? Whereas flatpak is a format and an entire toolkit for downloading and running flatpaks.

Now THAT is hip

Can you elaborate more on deduplication? Is this a feature you setup, or does it sort of work out of the box? This is a new concept to me, but sounds incredibly useful, especially in that scenario.

Perhaps I’m guilty of good luck, but is the trade off of performance for reliability worth it? How often is reliability a problem?

As a different use case altogether, suppose I was setting up a NAS over a couple drives. Does choosing something with COW have anything to do with redundancy?

Maybe my question is, are there applications where zfs/btrfs is more or less appropriate than ext4 or even FAT?

Keep it up. I enjoy hearing about the updates.