Skip to content

Latest commit

 

History

History
48 lines (36 loc) · 1.6 KB

build-tarball.adoc

File metadata and controls

48 lines (36 loc) · 1.6 KB

NixTurris tarball

Turris official system Turris OS is provided and installed using tarballs called "medkit". This is not it. This is really just a tarball with all files you need to unpack to the filesystem to install NixOS. It could potentially be used as "medkit" but on Omnia that would install it to internal flash (that is not desirable) and on Mox it installs it to subvolume @ which is not default configuration. TLDR this is not "medkit".

Building standard tarball

nix build github:cynerd/nixturris#tarballMox

Replace tarballMox with tarballOmnia for Turris Omnia.

The image is cross compiled in this case (unless you are running on the target platform).

Building custom tarball

If you already have NixOS configuration prepared (discussed in remote rebuild) for your device then you can generate tarball with it instead of standard one. The advantage is that you skip one step and you get prepared device immediately.

Unless you modified the initial template too much you can run the following command in the template directory to build your customized tarball:

nix build .#tarball

Native build using Qemu

For this to work you need to be running either on target platform (aarch64 for Mox and armv7l for Omnia) or you need to configure binfmt and Nix to run these architectures in emulation (Qemu). You can use option boot.binfmt.emulatedSystems on NixOS. Next you can just force a different build platform when building tarball.

nix build github:cynerd/nixturris#aarch64-linux.tarballMox