Nix as a static executable requiring no configuration, privileges, or (user) namespaces.
For binary downloads check the releases page.
Goals:
- make it extremely simple to install nix
- make nix work in restricted environments (containers, HPC, ...)
- be able to use the official binary cache (by simulating the /nix/store)
- make it easy to distribute nix (via other package managers)
Tested on the following systems/environments:
- Distros (x86_64):
- Arch Linux
- CentOS 7
- Debian
- Fedora
- NixOS
- Ubuntu
- Distros (aarch64):
- Debian
- Other Environments:
- Docker (debian image)
- Github Actions
Under the hood:
- The nix-portable executable is a self extracting archive, caching its contents in $HOME/.nix-portable
- Either bubblewrap or proot is used to simulate the /nix/store directory which actually resides in $HOME/.nix-portable/store
- A default nixpkgs channel is included and the NIX_PATH variable is set accordingly.
- Features
flakes
andnix-command
are enabled out of the box.
Drawbacks / Considerations:
If user namespaces are not available on a system, nix-portable will fall back to using proot instead of bubblewrap. Proot's virtualization can have a significant performance overhead depending on the workload. In that situation, it might be beneficial to use a remote builder or alternatively build the derivations on another host and sync them via a cache like cachix.org.
Missing Features:
- managing nix profiles via
nix-env
- managing nix channels via
nix-channel
- support MacOS
Executing nix-portable
After obtaining the binary, there are two options:
- Specify the nix executable via cmdline argument:
./nix-portable nix-shell ...
- Select the nix executable via symlinking, similar to busybox:
# create a symlink from ./nix-shell to ./nix-portable ln -s ./nix-portable ./nix-shell # execute nix-shell ./nix-shell
Executing installed programs
All programs installed via nix-portable will only work inside the wrapped environment. To enter the wrapped environment just use nix-shell:
nix-portable nix-shell -p bash
... or use nix run
to execute a program:
nix-portable nix run {flake-spec}
Container Runtimes
To simulate the /nix/store and a few other directories, nix-portable supports the following container runtimes.
- bwrap (existing installation)
- bwrap (shipped via nix-portable)
- proot (existing installation)
- proot (shipped via nix-portable)
bwrap is preferred over proot and existing installations are preferred over the nix-portable included binaries. nix-portable will try to figure out which runtime is best for your system. In case the automatically selected runtime doesn't work, use the follwing environment variables to specify the runtime, but please also open an issue, so we can improve the automatic selection.
Environment Variables
The following environment variables are optional and can be used to override the default behaviour of nix-portable
NP_DEBUG (1 = debug msgs; 2 = 'set -x' for nix-portable)
NP_GIT specify path to the git executable
NP_LOCATION where to put the `.nix-portable` dir. (defaults to `$HOME`)
NP_RUNTIME which runtime to use (must be 'bwrap' or 'proot')
NP_BWRAP specify the path to the bwrap executable to use
NP_PROOT specify the path to the proot executable to use
NP_RUN override the complete command to run nix
(to use an unsupported runtime, or for debugging)
nix will then be executed like: $NP_RUN {nix-binary} {args...}
Building / Contributing
To speed up builds, add the nix-portable cache:
nix-shell -p cachix --run "cachix use nix-portable"