Nix Installer
nix-installer is an opinionated, experimental Nix installer.
|
Status
nix-installer is pre-release and experimental. It is not ready for high reliability use! Please don't use it on a business critical machine!
Current and planned support:
- Multi-user Linux (aarch64 and x86_64) with systemd integration, no SELinux
- Root-only Linux (aarch64 and x86_64) with no init integration, no SELinux
- Multi-user MacOS (aarch64 and x86_64) with launchd integration
- SteamOS on the Valve Steam Deck
- Multi-user Linux (aarch64 and x86_64) with systemd integration & SELinux
- Others...
Installation Differences
Differing from the current official Nix installer scripts:
- Nix is installed with the
nix-commandandflakesfeatures enabled in thenix.conf nix-installerstores an installation receipt (for uninstalling) at/nix/receipt.jsonas well as a copy of the install binary at/nix/nix-installer
Motivations
The current Nix installer scripts do an excellent job, however they are difficult to maintain. Subtle differences in the shell implementations, and certain characteristics of bash scripts make it difficult to make meaningful changes to the installer.
Our team wishes to experiment with the idea of an installer in a more structured language and see if this is a worthwhile alternative. Along the way, we are also exploring a few other ideas, such as:
- offering users a chance to review an accurate, calculated install plan
- having 'planners' which can create appropriate install plans
- keeping an installation receipt for uninstallation
- offering users with a failing install the chance to do a best-effort revert
- doing whatever tasks we can in parallel
So far, our explorations have been quite fruitful, so we wanted to share and keep exploring.
Usage
Install Nix with the default planner and options:
|
Or, to download a platform specific Installer binary yourself:
nix-installerwill elevate itself if needed usingsudo. If you usedoasorpleaseyou may need to elevatenix-installeryourself.
nix-installer installs Nix by following a plan made by a planner. Review the available planners:
)
)
)
# ...
Planners have their own options and defaults, sharing most of them in common:
# ...
# ...
Planners can be configured via environment variable or command arguments:
| NIX_BUILD_GROUP_NAME=nixbuilder
# Or...
Uninstalling
You can remove a nix-installer-installed Nix by running
As a Github Action
You can use the nix-installer-action Github Action like so:
on:
pull_request:
push:
branches:
jobs:
lints:
name: Build
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v3
- name: Install Nix
uses: DeterminateSystems/nix-installer-action@main
- name: Run `nix build`
run: nix build .
In a container
In Docker/Podman containers or WSL instances where an init (like systemd) is not present, pass --init none.
When
--init noneis used, onlyrootor sudoers can run Nix:
For Docker containers (without an init):
# Dockerfile
FROM ubuntu:latest
RUN apt update -y
RUN apt install curl -y
COPY nix-installer /nix-installer
RUN /nix-installer install linux-multi --init none --no-confirm
ENV PATH="${PATH}:/nix/var/nix/profiles/default/bin"
RUN nix run nixpkgs#hello
Podman containers require sandbox = false in your Nix.conf.
For podman containers without an init:
# Dockerfile
FROM ubuntu:latest
RUN apt update -y
RUN apt install curl -y
COPY nix-installer /nix-installer
RUN /nix-installer install linux-multi --extra-conf "sandbox = false" --init none --no-confirm
ENV PATH="${PATH}:/nix/var/nix/profiles/default/bin"
RUN nix run nixpkgs#hello
For Podman containers with an init:
# Dockerfile
FROM ubuntu:latest
RUN apt update -y
RUN apt install curl systemd -y
COPY nix-installer /nix-installer
RUN /nix-installer install linux-multi --extra-conf "sandbox = false" --no-start-daemon --no-confirm
ENV PATH="${PATH}:/nix/var/nix/profiles/default/bin"
RUN nix run nixpkgs#hello
CMD [ "/usr/sbin/init" ]
In WSL
If systemd is enabled it's possible to install Nix as normal using the command at the top of this document:
|
If systemd is not enabled, pass --init none at the end of the command:
When
--init noneis used, onlyrootor sudoers can run Nix:
|
Building a binary
Since you'll be using nix-installer to install Nix on systems without Nix, the default build is a static binary.
Build a portable Linux binary on a system with Nix:
On Mac:
Then copy the result/bin/nix-installer to the machine you wish to run it on.
You can also add nix-installer to a system without Nix via cargo:
RUSTFLAGS="--cfg tokio_unstable"
To make this build portable, pass --target x86_64-unknown-linux-musl.
We currently require
--cfg tokio_unstableas we utilize Tokio's process groups, which wrap stablestdAPIs, but are unstable due to it requiring an MSRV bump.
As a library
Add nix-installer to your dependencies:
Building a CLI? Check out the
clifeature flag forclapintegration.
You'll also need to edit your .cargo/config.toml to use tokio_unstable as we utilize Tokio's process groups, which wrap stable std APIs, but are unstable due to it requiring an MSRV bump:
# .cargo/config.toml
[]
=["--cfg", "tokio_unstable"]
Then it's possible to review the documentation:
Documentation is also available via nix build: