Viewing profile — hinshun

No worries. I think Make vs Ninja is a whole another discussion but how it relates to this project is that Ninja has less features than Make (e.g. no globs, etc) which makes it att…

We're still missing this feature to fully incrementally compile nix: https://github.com/pdtpartners/nix-ninja/issues/19 Since there's a target that depends on a generated source fi…

I'm not sure, but we're in contact with some core Nix folks to see what we can do help move it along.

It made sense internally and we also thought it'll be compelling for people interested in Nix since Nix itself uses meson and outputs ninja. What other formats do you think are wor…

Hello, this is Edgar! We are open sourcing nix-ninja, an incremental build system for Nix that leverages dynamic derivations. For those unfamiliar, Nix is a powerful package manage…

Hi there! I am Edgar and I wanted to share with you “globset”, a Nix library to help specify what sources to include when building a Nix package using familiar glob patterns like “…

Happy to help. For EKS there’s a blog ( https://blog.realvarez.com/using-estargz-to-reduce-container... ) that goes into using stargz-snapshotter which will be same initial setup, …

Yes it’s going to depend on which k8s distribution you’re using. We have work in-progress for k3s to natively support nix-snapshotter: https://github.com/k3s-io/k3s/pull/9319 For o…

Author of nix-snapshotter here. Yes, one of the main downsides of Docker images using Nix is the 128 layer limit. It means we have to use a heuristic to combine packages into the s…

The EKS/GKE integration involves modifying the host that the kubelet lives and adding nix-snapshotter as a sibling host service. I didn’t mean running nix-snapshotter as a Kubernet…

Hi Alex, I’ve updated the README with a bit more information. 0 is actually an unbindable port, so nix:0 is just an arbitrary string that is unlikely to have conflicts. The Kubelet…

Yes! Our talk wasn’t accepted but Robbie and I, and a few others from my team will be there. Come say Hi!

Yup. If you also deploy the Nix packages to bare-metal, then creating containers is at almost zero cost because the container image component is just JSON.

We will be running it on a non-NixOS Kubernetes cluster, all you need is a nix daemon running as a systemd service. I have tested with EKS, and you should be able to use nix-snapsh…

Thank you! We appreciate it.

If you are comparing non-Nix image build performance, Nix is comparable to BuildKit in that it’s able to parallelize a build graph and cache intermediary outputs. Nix doesn’t requi…

That's fair, adding another service is definitely a downside. If you are running nix-built images though, the underlying data still needs to land somewhere on disk. Nix-snapshotter…

It can leverage de-duplication in your host nix store (as a sibling service to your container runtime), as opposed to having a containerized nix store each fetching its necessary p…

If you are pushing nix-snapshotter images to a Docker Registry, then it can only either use what's in your host nix store, or fetch from a binary cache. The same is true if you are…

Hi flurie, Nixery exposes an API (in the form of an Docker registry) to dynamically build Nix-based images, but still tar & compresses Nix packages into layer tarballs. Since the i…

Hello! This is Edgar and Robbie and we built nix-snapshotter. nix-snapshotter brings native understanding of Nix packages to containerd. We built this because Nix is a great fit fo…