Nixery – Docker images on the fly with Nix

• nixery

  6 1,543 2.1 Go

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

• fdb

  0 36 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.

• InfluxDB

  www.influxdata.com

  sponsored

  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

  4 534 4.1 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

  7 253 2.7 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

  3 267 6.8 Nix

  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

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

• naersk

  1 502 7.0 Nix

  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.

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

• Moby

  74 66,015 9.9 Go

  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.

• SonarQube

  www.sonarqube.org

  sponsored

  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

  4 443 1.3 Nix

  Build Android (AOSP) using Nix

  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