A Docker-compatible container registry that builds images on-demand using Nix package specifications from image names.
Nixery is a Docker-compatible container registry that builds container images on-demand using the Nix package manager. It allows users to specify packages as part of the image name, which Nixery then assembles into a container image with an optimized layer caching strategy. This solves the problem of manually writing Dockerfiles and ensures reproducible, declarative container images.
Developers and DevOps engineers using Nix for package management who want to generate container images directly from Nix packages, especially in environments prioritizing reproducibility and efficient caching.
Developers choose Nixery for its seamless integration with Nix, enabling declarative image specifications without Dockerfiles, and its intelligent layer sharing that reduces storage and build times across images.
Container registry which transparently builds images using the Nix package manager. Canonical repository is https://cs.tvl.fyi/depot/-/tree/tools/nixery
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows specifying packages directly in image names, eliminating manual Dockerfile authoring and ensuring reproducibility through Nix's deterministic builds.
Uses a layering strategy that prioritizes sharing popular or large dependencies, optimizing storage and reducing build times across different images as described in the README's layering strategy.
Supports building from custom git repositories or local filesystem paths, enabling organizations to use private package sets and version tags for tailored images.
Integrates with Google Cloud Storage, Amazon S3, or local filesystem backends for efficient layer serving, with support for signed URLs to enhance security.
Requires configuring multiple environment variables and setting up storage backends (e.g., GCS or S3), which can be nontrivial compared to using standard Docker registries.
Heavily relies on Nix and Nixpkgs, limiting usability for teams not invested in Nix or needing packages outside of the Nix ecosystem.
Focuses on package inclusion without support for arbitrary Dockerfile instructions like custom entry points or runtime configurations, which may require workarounds.
As noted in the roadmap, full Kubernetes integration is still in development, which could be a drawback for cloud-native deployments seeking seamless orchestration.