Nixery – Docker images on the fly with Nix

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • InfluxDB - Access the most powerful time series database as a service
  • SonarQube - Static code analysis for 29 languages.
  • SaaSHub - Software Alternatives and Reviews
  • nixery

    Container registry which transparently builds images using the Nix package manager. Canonical repository is

  • fdb

    FoundationDB client API for Tokio (by fdb-rs)

    That's correct. I recently ended up using `buildLayerImage` (actually `buildLayerImageWithNixDb` for CI, not only to run a single process, but also `systemd` and multiple processes. `podman` comes with built-in support for `systemd`.

    [Here]( is relevant code.

  • InfluxDB

    Access the most powerful time series database as a service. Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.

  • mobile-nixos

    Questions? #nixos-aarch64 (or #nixos) on Freenode!

    samueldr has been doing a lot of work in that direction. See

  • nix2container

    An archive-less dockerTools.buildImage implementation

    With, I'm trying to make a more standalone tool. Basically, a Go binary takes a reference graph and produces a JSON file describing a container image. This JSON file is then ingested by a Skopeo fork (it adds a new `transport`) to produce images (to file, registries,...).

    Currently, it supports the dockerTools layering algorithm and is designed to work with Guix [1] as well;)


  • crate2nix

    nix build file generator for rust crates

    Yes, you will have to package it if it's not already in nixpkgs.

    The good news is once you learn how, it's basically trivial with crate2nix[0], which can autogenerate nix derivations from rust crates


  • naersk

    Build rust crates in Nix. No configuration, no code generation, no IFD. Sandbox friendly. [maintainer: @Patryk27]

    You can also use naersk¹ if you want to avoid a two-step process. It's especially convenient when using nix flakes.


  • Moby

    Moby Project - a collaborative project for the container ecosystem to assemble container-based systems

    Thanks for clarify your point.

    > If you have two layers installing an individual packages like /nix/store/x and /nix/store/y, stacking them as [x, y] and [y, x] would result in the same docker image contents

    This is an assumption which is valid for nix, but not for most of the package managers. Whenever such assumption can be considered correct, Dockerfiles can achieve similar results using multiple stages, but you would probably need a pre-processor to have a stage for each package. Something like an `INCLUDE` directive could help too:

  • SonarQube

    Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.

  • robotnix

    Build Android (AOSP) using Nix

    Just noting, using Nix it is possible to build an actual real deal Android image using Robotnix:


    This is different from a non-Android Linux on Mobile devices, which is what Mobile NixOS aims to achieve :).

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts