nix3-run(1)

✨ nix3-run(1) β€” go run a Nix application, bestie ✨

hiiii so this is nix3-run(1) from the General Commands Manual, and it's literally the page that tells you how to make Nix go zoom and actually launch stuff. it's giving "cheat code for nix run" and honestly? iconic. πŸ’…

⚠️ Warning ⚠️ This program is experimental and its interface is subject to change. like, fr fr, the interface will change under your feet, so don't build your entire personality around it. 😭

πŸŽ€ Name

nix run β€” run a Nix application


πŸ’– Synopsis

nix run [option…] installable args…

🌸 Examples

  • Run the default app from the blender-bin flake:
# nix run blender-bin
  • Run a non-default app from the blender-bin flake:
# nix run blender-bin#blender_2_83
🫢 Tip: you can find apps provided by this flake by running nix flake show blender-bin.
  • Run vim from the nixpkgs flake:
# nix run nixpkgs#vim
🌟 Note that vim (as of the time of writing of this page) is not an app but a package. Thus, Nix runs the eponymous file from the vim package.
  • Run vim with arguments:
# nix run nixpkgs#vim -- --help
  • Run the default app from the current directory with arguments:
# nix run . -- arg1 arg2
πŸ’€ Note: The first positional argument is always treated as the installable, even after --. To pass arguments to the default installable, specify it explicitly: nix run . -- arg1 arg2 or nix run -- . arg1 arg2.

πŸ¦‹ Description

nix run builds and runs installable, which must evaluate to an app or a regular Nix derivation.

If installable evaluates to an app (see below), it executes the program specified by the app definition.

If installable evaluates to a derivation, it will try to execute the program <out>/bin/<name>, where out is the primary output store path of the derivation, and name is the first of the following that exists:

  • The meta.mainProgram attribute of the derivation.
  • The pname attribute of the derivation.
  • The name part of the value of the name attribute of the derivation.

For instance, if name is set to hello-1.10, nix run will run $out/bin/hello. ✨


🌈 Flake output attributes

If no flake output attribute is given, nix run tries the following flake output attributes:

  • apps.<system>.default
  • packages.<system>.default

If an attribute name is given, nix run tries the following flake output attributes:

  • apps.<system>.<name>
  • packages.<system>.<name>
  • legacyPackages.<system>.<name>

πŸ‘‘ Apps

An app is specified by a flake output attribute named apps.<system>.<name>. It looks like this:

apps.x86_64-linux.blender_2_79 = {
  type = "app";
  program = "${self.packages.x86_64-linux.blender_2_79}/bin/blender";
  meta.description = "Run Blender, a free and open-source 3D creation suite.";
};

The only supported attributes are:

  • type (required): Must be set to app.
  • program (required): The full path of the executable to run. It must reside in the Nix store.
  • meta.description (optional): A description of the app.

✨ Options ✨

🧠 Common evaluation options

  • --arg name expr β€” Pass the value expr as the argument name to Nix functions.
  • --arg-from-file name path β€” Pass the contents of file path as the argument name to Nix functions.
  • --arg-from-stdin name β€” Pass the contents of stdin as the argument name to Nix functions.
  • --argstr name string β€” Pass the string string as the argument name to Nix functions.
  • --debugger β€” Start an interactive environment if evaluation fails. (your lil debugging era 🫢)
  • --eval-store store-url β€” The URL of the Nix store to use for evaluation, i.e. to store derivations (.drv files) and inputs referenced by them.
  • --impure β€” Allow access to mutable paths and repositories.
  • --include / -I path β€” Add path to search path entries used to resolve lookup paths.

This option may be given multiple times. (stack 'em up πŸ’…)

Paths added through -I take precedence over the nix-path configuration setting and the NIX_PATH environment variable.

  • --override-flake original-ref resolved-ref β€” Override the flake registries, redirecting original-ref to resolved-ref.
  • --commit-lock-file β€” Commit changes to the flake's lock file.
  • --inputs-from flake-url β€” Use the inputs of the specified flake as registry entries.
  • --no-registries β€” Don't allow lookups in the flake registries.
🚫 DEPRECATED β€” Use --no-use-registries instead.
  • --no-update-lock-file β€” Do not allow any updates to the flake's lock file.
  • --no-write-lock-file β€” Do not write the flake's newly generated lock file.
  • --output-lock-file flake-lock-path β€” Write the given lock file instead of flake.lock within the top-level flake.
  • --override-input input-path flake-url β€” Override a specific flake input (e.g. dwarffs/nixpkgs). The input path must not be empty. This implies --no-write-lock-file.
  • --recreate-lock-file β€” Recreate the flake's lock file from scratch.
🚫 DEPRECATED β€” Use nix flake update instead.
  • --reference-lock-file flake-lock-path β€” Read the given lock file instead of flake.lock within the top-level flake.
  • --update-input input-path β€” Update a specific flake input (ignoring its previous entry in the lock file).
🚫 DEPRECATED β€” Use nix flake update instead.
  • --debug β€” Set the logging verbosity level to 'debug'.
  • --log-format format β€” Set the format of log output; one of raw, internal-json, bar or bar-with-logs.
  • --print-build-logs / -L β€” Print full build logs on standard error.
  • --quiet β€” Decrease the logging verbosity level. 🀫
  • --verbose / -v β€” Increase the logging verbosity level. πŸ“£

πŸŒ€ Miscellaneous global options

  • --help β€” Show usage information.
  • --offline β€” Disable substituters and consider all previously downloaded files up-to-date.
  • --option name value β€” Set the Nix configuration setting name to value (overriding nix.conf).
  • --refresh β€” Consider all previously downloaded files out-of-date.
  • --repair β€” During evaluation, rewrite missing or corrupted files in the Nix store. During building, rebuild missing or corrupted store paths.
  • --version β€” Show version information.

🌱 Options that change environment variables

  • --ignore-env / -i β€” Clear the entire environment, except for those specified with --keep-env-var.
  • --keep-env-var / -k name β€” Keep the environment variable name, when using --ignore-env.
  • --set-env-var / -s name value β€” Sets an environment variable name with value.
  • --unset-env-var / -u name β€” Unset the environment variable name.

🧚 Options that change the interpretation of installables

  • --expr expr β€” Interpret installables as attribute paths relative to the Nix expression expr.
  • --file / -f file β€” Interpret installables as attribute paths relative to the Nix expression stored in file. If file is the character -, then a Nix expression is read from standard input. Implies --impure.
πŸ“ Note See man nix.conf for overriding configuration settings with command line flags.

aaaand that's the whole page, bestie, you ate that πŸ“ the footer says nix3-run(1) β€” it's the nix3-run(1) page from the General Commands Manual, so like, that's the manual name and the version-of-record right there. now go run something cute. πŸ’œπŸ¦‹βœ¨

πŸ“¦ where this page comes from