From 6eb21bd3429535646da4aa396bb0c1f81a9b72c6 Mon Sep 17 00:00:00 2001 From: Edgar Lee <122112154+elpdt852@users.noreply.github.com> Date: Tue, 12 Sep 2023 16:03:10 +0200 Subject: [PATCH] Correct Nixery comparison with nixery-layers blog post (#98) --- README.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 44af4e2..4bb0107 100644 --- a/README.md +++ b/README.md @@ -354,11 +354,13 @@ store or fetched from your Nix binary cache. Answer Nixery exposes an API (in the form of an OCI registry) to dynamically build -Nix-based images, but still uses the same layering strategy as upstream's -`pkgs.dockerTools.buildImage` (see above). So Nixery suffers from the same -inefficiency in duplication. However, Nixery can totally start building +Nix-based images. It has an [improved layering design][nixery-layers] compared +to upstream `pkgs.dockerTools.buildImage` but is still fundamentally a +heuristics- based layering strategy (see above), so it still suffers from the +same inefficiency in duplication. However, Nixery can totally start building nix-snapshotter images so we can have a Docker Registry that can dynamically -build native Nix images. +build native Nix images. See this [Nixery issue][nixery-issue] to follow along +the progress. @@ -433,6 +435,8 @@ details. [nix2container]: https://github.com/nlewo/nix2container [nix-command]: https://zero-to-nix.com/concepts/nix#unified-cli [nixery]: https://nixery.dev/ +[nixery-issue]: https://github.com/tazjin/nixery/issues/160 +[nixery-layers]: https://tazj.in/blog/nixery-layers [nix-flake]: https://zero-to-nix.com/concepts/flakes [nix]: https://nixos.org/ [nix-installer]: https://zero-to-nix.com/start/install