Nix / NixOS
Homebrew is the most popular package manager on MacOS, and for good reason. However personally, I believe that Nix is more powerful.
*edit: for the solution, see my comment below* I need/want to build [aeson](https://github.com/haskell/aeson/) and its subproject *attoparsec-aeson* from source (it's a fork of the "official" *aeson*), but I'm stuck... can you help out? The sources of *attoparsec-aeson* live in a subdirectory of the *aeson* ones, so I have the sources: ```nix aeson-src = fetchFromGitHub { ... }; ``` and the "main" *aeson* library: ```nix aeson = haskellPackages.mkDerivation { pname = "aeson"; src = aeson-src; ... }; ``` When I get to *attoparsec-aeson* however I run into a wall: I tried to follow the [documentation about `sourceRoot`](https://ryantm.github.io/nixpkgs/stdenv/stdenv/#var-stdenv-sourceRoot): ``` attoparsec-aeson = haskellPackages.mkDerivation { pname = "attoparsec-aeson"; src = aeson-src; sourceRoot = "./attoparsec-aeson"; # maybe this should be "${aeson-src}/attoparsec-aeson"? # (it doesn't work either way) ... }; ``` but I get ```plaintext error: function 'anonymous lambda' called with unexpected argument 'sourceRoot' ``` Did I fail to spot some major blunder (I am nowhere near an expert)? Does `sourceRoot` not apply to `haskellPackages.mkDerivation`? What should I do to make it work? BTW: IDK if this may cause issues, but the `attoparsec-aeson` sources include symlinks to files in the "main" `attoparsec` sources: ```shell ~/git-clone-of-attoparsec-sources $ tree attoparsec-aeson/ attoparsec-aeson/ ├── src │ └── Data │ └── Aeson │ ├── Internal │ │ ├── ByteString.hs -> ../../../../../src/Data/Aeson/Internal/ByteString.hs │ │ ├── Text.hs -> ../../../../../src/Data/Aeson/Internal/Text.hs │ │ └── Word8.hs -> ../../../../../src/Data/Aeson/Internal/Word8.hs │ ├── Parser │ │ └── Internal.hs │ └── Parser.hs ├── attoparsec-aeson.cabal └── LICENSE ```
I believe I solved this problem before, but I can't find the solution again. I have some Flatpaks installed on my NixOS system, but they aren't showing up in the app menu. Does anyone know what might be causing this or how to fix it?
wastedintel.ca
cross-posted from: https://discuss.tchncs.de/post/22584651
[Self-hosted photo and video management solution](https://immich.app/)
I'm trying to set up a simple script (linked to a hotkey in my window manager) that can launch a terminal window with a nix-shell containing packages I specify. So far, I got this: ```fish set packages (fuzzel -d --lines 0 --prompt 'packages for nix-shell > ') kitty nix-shell --packages $packages --run fish ``` If I type a single package into my runlauncher (fuzzel) (e.g. `grim`), the window spawns with a nix-shell as expected; if, however, I attempt to launch a shell with multiple packages (e.g. `grim slurp`), it fails to launch with the following error: ```nix error: … while calling the 'derivationStrict' builtin at /builtin/derivation.nix:9:12: (source not available) … while evaluating derivation 'shell' whose name attribute is located at /nix/store/cjz8w4dgc3rd2n3dqv5c208vygndjyba-source/pkgs/stdenv/generic/make-derivation.nix:336:7 … while evaluating attribute 'buildInputs' of derivation 'shell' at /nix/store/cjz8w4dgc3rd2n3dqv5c208vygndjyba-source/pkgs/stdenv/generic/make-derivation.nix:383:7: 382| depsHostHost = elemAt (elemAt dependencies 1) 0; 383| buildInputs = elemAt (elemAt dependencies 1) 1; | ^ 384| depsTargetTarget = elemAt (elemAt dependencies 2) 0; error: attempt to call something which is not a function but a set at «string»:1:107: 1| {...}@args: with import <nixpkgs> args; (pkgs.runCommandCC or pkgs.runCommand) "shell" { buildInputs = [ (grim slurp) ]; } "" | ^ ``` This happens with or without launching a new kitty window, and it happens with other runlaunchers as well. Why on earth isn't this working? Any help appreciated---thanks, everyone.
cross-posted from: https://discuss.tchncs.de/post/22526287
cross-posted from: https://discuss.tchncs.de/post/22434175
discourse.nixos.org
cross-posted from: https://discuss.tchncs.de/post/22389417
discourse.nixos.org
cross-posted from: https://discuss.tchncs.de/post/22368053 > NixOS Facter aims to be an alternative to projects such as [NixOS Hardware](https://github.com/NixOS/nixos-hardware) and [nixos-generate-config](https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/installer/tools/nixos-generate-config.pl). It solves the problem of bootstrapping [NixOS configurations](https://nixos.org/manual/nixos/stable/#sec-configuration-syntax) by deferring decisions about hardware and other aspects of the target platform to NixOS modules.
Maaaybe a stupid question as it might just be the same thing done differently. I'm not bright enough to understand the differences. ```hardware.graphics``` was recently introduced which replaced ```hardware.opengl```. Now, I've got my ```amdvlk```, ```libva``` and such configured via ```hardware.graphics``` — recently I came across ```hardware.amdgpu``` which offers a bunch of options. Should one combine, use one or the other, or does it make any difference at all? ``` hardware.amdgpu.opencl.enable hardware.amdgpu.legacySupport.enable hardware.amdgpu.initrd.enable hardware.amdgpu.amdvlk.supportExperimental.enable hardware.amdgpu.amdvlk.support32Bit.package hardware.amdgpu.amdvlk.support32Bit.enable hardware.amdgpu.amdvlk.settings hardware.amdgpu.amdvlk.package hardware.amdgpu.amdvlk.enable hardware.graphics.extraPackages32 hardware.graphics.extraPackages hardware.graphics.enable32Bit hardware.graphics.enable ``` That is, are these two examples the same for all intents and purposes or do either bring anything else? ``` hardware.amdgpu.amdvlk = { enable = true; support32Bit.enable = true; }; # VS. hardware.graphics = { enable = true; enable32Bit = true; extraPackages = with pkgs; [ amdvlk ]; extraPackages32 = with pkgs; [ driversi686Linux.amdvlk ]; }; ```
Title says it all. The Determinate Systems installer is supposed to have support, but it doesn’t work – from what I can tell, the contexts are wrong. Running `restorecon` reports changes, but I’m still getting denials. Running on Fedora Asahi Remix 40, if that’s relevant. Is there any way to make this work? AppArmor is unsupported on Fedora, so I can’t switch to it…
Hi all; This is a bit of a long shot; but I'm having an issue with trying to modularize my config in preparation for a new laptop. In particular the issue I have is around passing a path through to an import statement for a home-managed user. In particular I'm getting undefinedVariable hmPath; but it doesn't seem to be having the same issue when I'm mapping groups and shell; so I can only assume that imports has to be treated differently but I'm at a loss. Any help on what I've misunderstood would be greatly appreciated. Snippet below ``` { pkgs, config, options, lib, home-manager, ... }: with lib; let cfg = config.ltp.home; user = types.submodule ({name, ...}: { options = { doas.enable = mkEnableOption { default = false; type = types.bool; }; groups = mkOption { default = []; type = types.listOf string; }; shell = mkOption { default = pkgs.bash; type = types.package; }; hmPath = mkOption { type = types.path; }; }; }); in { options.ltp.home = { users = mkOption { description = Attrset of home-manager users; default = {}; type = types.attrsOf user; }; }; config = mkIf (cfg.users != {}) (mkMerge [ { users.users = let mkUser = lib.attrsets.mapAttrs' ( name: value: lib.attrsets.nameValuePair "${builtins.baseNameOf name}" { isNormalUser = true; extraGroups = "${groups}"; shell = "${shell}"; } ) cfg.users; in mkUser; home-manager.users = let mkHmUser = lib.attrsets.mapAttrs' ( name: value: lib.attrsets.nameValuePair "${builtins.baseNameOf name}" { imports = [ "${hmPath}" ]; } ) cfg.users; in mkHmUser; } ]); } ``` Edit... Solved the initial issue I was confusing myself and should've been using value.hmPath and equivalent inside the lib functions. Next issue; I'm having is I can't seem to pass through the path for the home-manager module for the user that is give to the import statement. Edit 2... I didn't manage to get it working how I was doing it so I've changed my approach; to implicitly reference the users home-manager base module based on the folder structure e.g. ./hosts/${hostname}/users/${builtins.baseNameOf name}
Just a short elevator pitch that was posted today in that 100 seconds format. Maybe useful in introducing others.
A big part of why nix documentation is sub par. The essential tomes of nix - the nix manual, the nixos manual, the nixos options, the nixpkgs manual - each of these documents is just one long page. They are the digital equivalent of scrolls, rather than books ([codices](https://en.wikipedia.org/wiki/Codex)?). Rather than having a page number (or page link), one must unroll the scroll to the point of interest. One cannot simply flip between two points of interest. One cannot have bookmarks, or refer to page numbers. Ctrl-F is helpful, sure, but not great. For instance, I was just looking for the documentation of the systemd.services.<name> options. Its near the end of the colossally long scroll known as the Nixos Options Appendix. Ctrl-F on systemctl.services will get one million hits on all the myriad services nixos offers before you finally get to the relevant section. And if you do find that section (with single pixel movements of the scroll bar) and then ctrl-f, woe betide you, you're now at the top of the document and your place is lost!
Hi! I've ran into an issue with `nix develop` shells. My setup: - Nix Darwin (macos) - Custom TLS certificates installed via nix darwin Everything works as expected with the installed certificates, but as soon as I enter into a development shell with `nix develop`, the certificates are not available and thus, I get TLS errors that break whatever I'm doing in the dev shell. If I use an impure development shell, the issue disappears. Is there a way to use pure `nix develop` shells which respect the installed certificates?
I had been struggling for a while to get CUDA on my main NixOS box for some ML programming. It seems there weren't any clear solutions in the NixOS forums, which just suggested suffering through painful build times. Here's my hacky, less Nix-y approach that takes ~5 minutes.
I followed the wiki on libvirt https://nixos.wiki/wiki/Libvirt and even set up the config for qemu for uefi but it isn't recognizing it I guess. Any ideas? Thanks
I want to change my hardware config from 2 btrfs partitions to 1 partition with subvolumes for root, /nix, /home, and maybe some other like /log. I mainly want to optimize the /nix/store. And possibly being ready to integrate the [impermanence](https://github.com/nix-community/impermanence) module down the line What would be the easiest way to accomplish this without reinstalling or breaking too much? Alternativly I thought about using [disko](https://github.com/nix-community/disko) and `nixos-install` the overwrite my second disk Thank you
I'm using Nixos 24.05 on my asus zenbook 14 and the scroll speed of the touchpad is rather high. Is there any way to adjust it from the config? I don't see an option in gnome/wayland
This description is a repost of what was said about the project on the nix discourse SkaraboxOS provides a flake template which combines: - Creating a bootable ISO, installable on an USB key. - nixos-anywhere to install NixOS headlessly. - disko 1 to format the drives. - deploy-rs 2 to deploy updates. SkaraboxOS expects a particular hardware layout: - 1 SSD or NVMe drive for the OS. - 2 Hard drives that will store data. Capacity depends on the amount of data that will be stored. They will be formatted in Raid 1 (mirror) so each hard drive should have the same size. WARNING: The 3 disks will be formatted and completely wiped out of data. At the end of the process, the server will: - Have an encrypted ZFS root partition using the NVMe drive, unlockable remotely through ssh. - Have an encrypted ZFS data hard drives. - Be accessible through ssh for administration and updates. [discourse post](https://discourse.nixos.org/t/skaraboxos-opinionated-nixos-installer/50138)
Hi! I would like to host a transparent proxy for cache.nixos.org on my local kubernetes cluster. I took the following NGINX config https://nixos.wiki/wiki/FAQ/Private_Cache_Proxy and created all the folders on the mounted storage. This is the kubernetes deployment: ```yaml apiVersion: v1 kind: PersistentVolume metadata: name: nix-cache-volume spec: capacity: storage: 500Gi storageClassName: manual accessModes: - ReadWriteOnce hostPath: path: "/mnt/k8s/nix-cache" # Needs exists before PV is created! persistentVolumeReclaimPolicy: Retain --- apiVersion: v1 kind: PersistentVolumeClaim metadata: name: nix-cache-pvc spec: accessModes: - ReadWriteOnce storageClassName: manual resources: requests: storage: 500Gi --- apiVersion: apps/v1 kind: Deployment metadata: name: nix-cache spec: replicas: 1 selector: matchLabels: app: nix-cache template: metadata: labels: app: nix-cache name: nix-cache spec: volumes: - name: nix-cache-storage persistentVolumeClaim: claimName: nix-cache-pvc - name: nix-cache-config configMap: name: nix-cache-config containers: - name: nix-cache image: nginx:1.27.0 ports: - containerPort: 80 volumeMounts: - name: nix-cache-storage mountPath: /data - name: nix-cache-config mountPath: /etc/nginx/sites-available/default resources: limits: memory: "512Mi" cpu: "300m" requests: memory: "256Mi" cpu: "200m" --- apiVersion: v1 kind: Service metadata: name: nix-cache spec: selector: app: nix-cache ports: - protocol: TCP port: 80 targetPort: 80 --- apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: nix-cache-ingress annotations: traefik.ingress.kubernetes.io/router.tls: "true" spec: rules: - host: "nix-cache.raspi.home" http: paths: - pathType: Prefix path: "/" backend: service: name: nix-cache port: number: 80 tls: - secretName: nix-cache-raspi-home-tls hosts: - "nix-cache.raspi.home" --- apiVersion: cert-manager.io/v1 kind: Certificate metadata: name: nix-cache.raspi.home spec: commonName: nix-cache.raspi.home dnsNames: - "nix-cache.raspi.home" secretName: nix-cache-raspi-home-tls issuerRef: name: ca-issuer kind: ClusterIssuer --- apiVersion: v1 kind: ConfigMap metadata: name: nix-cache-config data: nginx.conf: | server { listen 80; server_name nix-cache.raspi.home; location ~ ^/nix-cache-info { proxy_store on; proxy_store_access user:rw group:rw all:r; proxy_temp_path /data/nginx/nix-cache-info/temp; root /data/nginx/nix-cache-info/store; proxy_set_header Host "cache.nixos.org"; proxy_pass https://cache.nixos.org; } location ~^/nar/.+$ { proxy_store on; proxy_store_access user:rw group:rw all:r; proxy_temp_path /data/nginx/nar/temp; root /data/nginx/nar/store; proxy_set_header Host "cache.nixos.org"; proxy_pass https://cache.nixos.org; } } ``` To use the cache I added it to the `substituters`. ```nix nix.settings.substituters = [ "https://nix-cache.raspi.home/" ]; ``` But when I try to use it, get the error: ```bash # Trigger a download nix develop nixpkgs#just # Error message warning: 'https://nix-cache.raspi.home' does not appear to be a binary cache ``` In the logs of the NGINX I see the following error: ``` 2024/08/03 12:09:30 [error] 31#31: *3 open() "/usr/share/nginx/html/nix-cache-info" failed (2: No such file or directory), client: 10.42.2.7, server: localhost, request: "GET /nix-cache-info HTTP/1 │ │ 10.42.2.7 - - [03/Aug/2024:12:09:30 +0000] "GET /nix-cache-info HTTP/1.1" 404 153 "-" "curl/8.8.0 Nix/2.18.5" "10.42.2.1" │ │ 10.42.2.7 - - [03/Aug/2024:12:09:30 +0000] "PUT /nix-cache-info HTTP/1.1" 405 157 "-" "curl/8.8.0 Nix/2.18.5" "10.42.2.1" ``` Any ideas whats wrong? I'm neither an nix nor an nginx expert, so maybe it is something really simple but I cannot figure it out.
I am having audio issues on NixOS. I have tried enabling all firmware. I've also tried both pipewire and pulseaudio. The audio is confirmed working on CachyOS live image. Here is the error message found in the system log: `Aug 01 01:43:19 nixos kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: sink MIXER1.0g623.1 not found Aug 01 01:43:19 nixos kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: topology: add_route failed: -22 Aug 01 01:43:19 nixos kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: topology: could not load header: -22 Aug 01 01:43:19 nixos kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: tplg component load failed -22 Aug 01 01:43:19 nixos kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to load DSP topology -22 Aug 01 01:43:19 nixos kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_component_probe on 0000:00:1f.3: -22 Aug 01 01:43:19 nixos kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to instantiate card -22 Aug 01 01:43:19 nixos kernel: skl_hda_dsp_generic skl_hda_dsp_generic: probe with driver skl_hda_dsp_generic failed with error -22` Here is [configuration.nix](https://pastebin.com/cBfvfhWR)
I created a hyprland and waybar configuration using nix, and neither seem to actually apply. Why is this happening? https://pastebin.com/01z6BiCj
Does anybody know if there is a website or resource that has NixOS modules you can include in your config?
This is my first FOSS code project. If anyone has any constructive suggestions for improvement, please let me know. [https://github.com/guttermonk/waybar-nixos-updates](https://github.com/guttermonk/waybar-nixos-updates)
I am just setting up my NixOS config for the first time, and I know that it will be fairly complex. I know it will only be possible and scalable if I have sane conventions. I have read a number of example configs, but there does not seem to be consistent conventions between them of where to store custom option declarations, how to handle enabling/disabling modules, etc. They all work, but they do it in different ways. Are there any official or unofficial conventions/style guides to NixOS config structure, and where can I find them? For example, should I make a `lib` directory where I put modules that are easily portable and reusable in other people's configs? When should I break modules up into smaller ones? Etc. These are things that I hope to be addressed.
So I started using nixos as a daily driver several months ago. At first it was nice using the life disk to install it. I really liked the options you could choose. The only the thing it misses is the information that it will install systemd bootloader and I don't have the option to install grub2. Then when I used it I had to learn that I needed to switch my flatpaks back to the system packages since nix had almost all of them too. And nix packages work better in nix. Even though flatpak is sandboxed sth. in nixos makes some of them break. I could usually install my software just by using the existing packages, but if not available I started learning nix-shell amd nix in general. This is when I realised I can't recommend nixos to normal people. If for any reason you need to install sth. that is not in the packages you are fucked. Usually it is easier to get a docker running than to learn nixos and setup a working nix-shell. However once you have a nix-shell to compile some c program you definitely have a deeper understanding of nixos and the program. I often break my systems by tinkering around. So this was a great experience in nixos since I could go back several generations to a working one and continue from there. However the last weeks I managed to break nixos! Even going back several generations didn't help. Probably going back several weeks may have worked, but I decided to reinstall instead. So my problem was basically that I updated from 23.11 to 24.05. I wanted to update since I was on unstable for razer stuff since I need current drivers. However once I managed to get the update working i wasn't able to login into x11 anymore and Wayland seems inperformant in gaming. I also have other issues with Wayland. The next thing was that I wanted to use an amd gpu for gpu-passthrough in a vm and therefore had a Nvidia and amd gpu present. However the system booted into the amd gpu and only after login switched to the Nvidia one. If I blacklisted the drivers of amd I would not get a sddm log in screen anymore. Nothing I did fixed that. Removing the amd gpu didn't help. Going back to the novau drivers worked but I couldn't use them since they are broken as well. After tinkering around a lot I finally decided to reinstall the current nixos image. So life image it is again. Automatically loads Wayland. If I assume correctly with novau drivers. I installed everything however during the installation process the gui broke. (Wayland and novau don't work well I guess. Fuck Nvidia) And even though through tty I could see when it was finished I couldn't boot into the system. So I rebooted the life disk and then logged out switched to x11 and reinstalled again. This time it worked. I then used my old configuration and only updated to plasma6 since I already installed that on the new installation. And to my surprise it just worked. Everything was like before. X11 working and so on. So while I managed to break nixos it is in fact just as easy to reinstall again and configure like before.
Hi, I am considering switching to NixOS and I was wondering what level of hassle I should expect for gaming. I have been using linux for about 10 months so I don't know a lot yet. I am wondering if it is worth it to try gaming on Nix or if it is going to be way too much of a headache considering my limited knowledge. I've had wildly different experiences trying gaming on different distros, and very differently from what I expected. It went from fine for a weird niche distro (antiX), to really awful for a distro supposedly "easy" and "good for gaming" (Manjaro 😑), to absolutely amazing gaming distro (Nobara), and finally to surprisingly good for a "don't try unless you are a Level 99 Tech Wizard dual-classed Zen Master you idiot" distro (Arch). So I really have no clue what to expect from Nix. I really like Arch but my main issue is that I keep forgetting what I have already configured and how and with which settings, or I leave stuff partially configured because adhd then I forget it wasn't finished and where I was at, so using config files instead sound insanely more convenient and I've been wanting to try Nix for a while. I'd be really glad for anyone willing to share their experience of gaming on Nix 🙂
I have started using NixOS recently and I am just now creating conventions to use in my config. One big choice I need to make is whether to include a unique identifier as the most significant attribute in any options that I define for my system. For example: Lets say I am setting up my desktop so that I am easily able to switch between light and dark modes system-wide. Therefore, I create the boolean option: `visuals.useDarkMode` Lets say I also want to toggle on/off Tor and other privacy technologies all at once easily, so I create the boolean: `usePrivateMode` Although these options do not do related things, they are still both custom options that I have made. I have the first instinct to somehow segregate them from the builtin NixOS options. Let's say my initials are "RK". I could make them all sub-attributes of the "RK" attribute. `rk.visuals.useDarkMode` `rk.usePrivateMode` I feel like this is either a really good idea or an antipattern. I would like your opinions on what you think of it and why.