bundlers

So I so far use it for dev environment and also for CI pipeline (the benefit is that Nix allows caching between runs, it helps with things like: - getting dev environment on CI to be identical to user dev - with minor changes the project is not rebuilt or or rebuilt minimally - the caching works across branches, so for example merging a feature branch to master, if nothing changes the build on master will be very quick I created something similar to nix-cache for gitlab, but I had to create a dedicated runner running NixOS. If I could use NixOS for deployment, at that point I would just point the same binary cache to the machine and use the same derivation to build the app. Because the app was already build by CI, it would just download the compiled version. No need for artifactory or similar. In that scenario (you using poetry) you proba

On systems that have the same containerization feature that Docker requires, i.e., Linux systems with recent kernels, you can use nix-bundle¹ or the flakes-based experimental command inspired by it, `nix bundle`² to generate an all-in-one binary that you can run without installing Nix on the target. 1: https://github.com/matthewbauer/nix-bundle 2: https://github.com/NixOS/bundlers

We've seen the opposite. New package managers are built with a much better understanding of the problem space because of Nix and sometimes explicitly taking ideas and concepts. This results in those new systems being far more compatible and easily integrated with Nix itself. Consider the iteration towards better and better locking in python + Node. Consider Rust/Cargo. There has also been sharing of ideas and collaboration between things us and bazel/buck/spack/etc. I think it is clear that we are all moving towards a similar end state, that often looks very much like Nix, or a re-invention of it. For things like OCI, Nix predates it, but we should start to re-use the standard. The Tvix group is exploring this and I'd suspect our sandboxing will be OCI at some point. For outputs; we make it easy to convert a Nix package into an equivalent

Nix 3 has a dead simple, builtin CLI frontend for doing this with built packages: https://nixos.org/manual/nix/unstable/command-ref/new-cli/ni... It uses dockerTools: https://github.com/NixOS/bundlers/blob/master/flake.nix maybe a bundler can be added that uses OCI tools, thus providing such a wrapper and giving a nice CLI for it

With the new (nominally experimental) CLI, use `nix bundle --bundler github:NixOS/bundlers#toArx` (or equivalently just `nix bundle`) to build a self-extracting shell script[1], `...#toDockerImage` to build a Docker image, etc.[2,3], though there’s no direct AppImage support that I can see (would be helpful to eliminate the startup overhead caused by self-extraction). If you want a QEMU VM for a complete system rather than a set of files for a single application, use `nixos-rebuild build-vm`, though that is intended more for testing than for deployment. The Docker bundler seems to be using more general Docker-compatible infrastructure in Nixpkgs[4]. [1] https://github.com/solidsnack/arx [2] https://nixos.org/manual/nix/unstable/command-ref/new-cli/ni... [3] https://github.com/NixOS/bundlers [4] https://nixos.org/manual/nixpkgs/stable/#sec