nixos-and-flakes-book
distrobox
nixos-and-flakes-book | distrobox | |
---|---|---|
9 | 403 | |
1,537 | 9,061 | |
- | - | |
9.6 | 9.6 | |
9 days ago | 6 days ago | |
Nix | Shell | |
Creative Commons Attribution Share Alike 4.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nixos-and-flakes-book
-
NixOS: Declarative Builds and Deployments
I'll be honest, the first few times I tried using Nix I just couldn't get into. It was too complex for the benefits I was getting. But that was using Nix on another OS.
I recently switched to NixOS because I wanted what they were selling and the experience this time around was way better. Having no other option but to figure it out made me learn the essentials real quick (like an exchange program to a foreign country that speaks another language).
If you think about it, when you used Ubuntu or Fedora or RHEL for the first time, and probably for a very long time, you could get by without learning the deep intricacies of what is going on behind the scenes. The same is true with NixOS. The things you need to learn are different, but once you get a basic setup with home-manager setup you're off to the races. (Btw, I used this "book" to get started and it was great: https://nixos-and-flakes.thiscute.world/)
The best part about using NixOS so far is that things just work. Setting up my graphics card was as simple setting enabled = true. Same for configuring specific audio frameworks. And I had tried many times to get Davinci Resolve working on other distros and always encountered issues leading me to need to dual-boot Windows so I could do video editing. Now I just enabled Davinci Resolve and it works! No more Windows.
If you're brand new to linux on the desktop, I wouldn't recommend it. But if you've been doing that for years, maybe try NixOS in 2024.
-
What is the current recommended documentation when starting out with NixOs?
i'm new to nixos too, i found this
-
Flakes Question (because I'm a noob)
I found this guide really beginner friendly: https://nixos-and-flakes.thiscute.world/
-
NixOS and Flakes Book: An unofficial book for beginners (free)
their GH releases page has a PDF, if that helps you, or browsing around the .md files may help what I presume is your noscript browser, assuming that GH works with noscript anymore: https://github.com/ryan4yin/nixos-and-flakes-book/releases/d...
- NixOS and Flakes Book
-
NixOS Wiki – the unofficial user wiki
It would be useful if the wiki articles showed a 'last modified at' date. Articles like this [0] dominate search results, but it's not clear how outdated the info is. I
In case anyone is looking for an up-to-date NixOS guide/cookbook, I've found lots of value in this [1] resource.
[0] - https://nixos.wiki/wiki/PulseAudio
[1] - https://nixos-and-flakes.thiscute.world/
- GitHub - ryan4yin/nixos-and-flakes-book: An unofficial NixOS & Flakes book for Beginners.
- Updates: NixOS & Nix Flakes - A Guide for Beginners
distrobox
-
Show HN: Convert your Containerfile to a bootable OS
That seems more like Distrobox to me(?) https://distrobox.it/
-
Windows 11 now comes with its own adware
Regarding the stability issue on a dev machine - you may be interested in playing with one of the immutable-os distros, such as SilverBlue (fedora based).
The high-level take-away is you can't break your actual OS since it's root filesystem is read-only, and you use "pet" containers (on docker, podman, whatever) to do your work in. Applications are either sandboxed via Flatpak, or installed/run inside your pet containers. If your pet container dies, you cry about it for a moment, and when you're ready you get a new one - your actual os and other containers remain unaffected.
I use distrobox[1] to create/run the pet containers.
[1] https://github.com/89luca89/distrobox
-
Tools for Linux Distro Hoppers
Distrobox is a tool that enables us to try Linux distro CLI, including their package manager. This requires a containerization tool (e.g., Docker). In Windows, this can be achieved using WSL (Windows Subsystem for Linux)
- Distrobox: Use any Linux distribution inside your terminal
-
Fedora Atomic Desktops
I use containerized versions of things, ubuntu and chainguard images mostly.
You can always create containers with init if that's how you want to do that though. Some distros publish images that come that way: https://github.com/89luca89/distrobox/blob/main/docs/useful_...
-
Raspberry Pi is manufacturing 70K Raspberry Pi 5s per week
https://news.ycombinator.com/item?id=38505448 ... https://github.com/89luca89/distrobox/blob/main/docs/useful_...
-
Operating System?
Yes, you can do that but I've seen others use something like distrobox to run linux inside of SteamOS: https://github.com/89luca89/distrobox/blob/main/docs/posts/steamdeck_guide.md
-
How much will I screw up my system after installing Merkuro Calendar (KDE Akonadi application), formerly called Kalendar, on GNOME?
For such cases you might use something like this: https://github.com/89luca89/distrobox
-
Battery consumption of using remote development with WSL2?
Btw #3: Depending on what the user is trying to accomplish, e.g. maybe to make WSL(2) itself more of a "subsystem" than a "container engine", using something like Distrobox or nsbox.dev can be a good idea (along with Docker or Podman in Distrobox's case; the other one uses systemd-nspawn).
-
Cannot run containers with Distrobox
1. Find here in "Containers Distros" section the distro image that you want to install ("Toolbox" versions are better because they are configured for Distrobox) and get it URL: https://distrobox.it/compatibility/#containers-distros 2. Use that URL to create Distrobox: distrobox create -i registry.fedoraproject.org/fedora-toolbox:39 -n fedora_1_39 3. Enter Distrobox fedora_1_39: distrobox enter fedora_1_39 4. You are already in Distrobox console. Look at the name in console, it should be include the container name. 5. To exit Distrobox: exit 6. If you run: distrobox list you will see all distroboxes on the system. You will also see that distrobox that we exited is still running. 7. To stop distrobox use commands: distrobox stop fedora_1_39
What are some alternatives?
nix-config - ❄️ my nix config for both desktops(NixOS+macOS) and homelab servers(NixOS).
toolbox - Tool for interactive command line environments on Linux
wiki - Nixos wiki [maintainer=@samueldr]
wsl-distrod - Distrod is a meta-distro for WSL 2 which installs Ubuntu, Arch, Debian, Gentoo, etc. with systemd in a minute for you. Distrod also has built-in auto-start feature on Windows startup and port forwarding ability.
rfcs - The Nix community RFCs
docker-android - Android in docker solution with noVNC supported and video recording
vitepress - Vite & Vue powered static site generator.
flatpak - Linux application sandboxing and distribution framework
nix-starter-configs - Simple and documented config templates to help you get started with NixOS + home-manager + flakes. All the boilerplate you need!
rustdesk - An open-source remote desktop, and alternative to TeamViewer.
nixos-wsl-starter - A sane, batteries-included starter template for running NixOS on WSL
toolbox-vscode - Toolbox Visual Studio Code integration