Nixery – Docker images on the fly with Nix

• nixery

  18 1,685 4.8 Go

  Container registry which transparently builds images using the Nix package manager. Canonical repository is https://cs.tvl.fyi/depot/-/tree/tools/nixery

• fdb

  1 41 0.0 Rust

  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](https://github.com/fdb-rs/fdb/blob/fdb-0.2.2/nix/ci/flake.ni...) is relevant code.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• mobile-nixos

  12 713 8.9 C

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

  

samueldr has been doing a lot of work in that direction. See https://mobile.nixos.org/

• nix2container

  9 430 6.3 Go

  An archive-less dockerTools.buildImage implementation

With https://github.com/nlewo/nix2container, 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;)

[1] https://github.com/nlewo/nix2container/blob/065e5b108650ee4c...

• crate2nix

  10 317 9.4 Nix

  rebuild only changed crates in CI with crate2nix and nix

  

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

[0] https://github.com/kolloch/crate2nix

• naersk

  6 635 5.6 Nix

  Build Rust projects in Nix - no configuration, no code generation, no IFD, sandbox friendly.

  

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

¹https://github.com/nix-community/naersk

• Moby

  212 67,716 10.0 Go

  The 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: https://github.com/moby/moby/issues/3378.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• robotnix

  14 562 6.8 Nix

  Build Android (AOSP) using Nix [maintainer=@danielfullmer,@Atemu]

  

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

- https://github.com/danielfullmer/robotnix/

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

Suggest a related project