nix2container
nixpacks
nix2container | nixpacks | |
---|---|---|
9 | 17 | |
453 | 2,172 | |
- | 5.1% | |
6.3 | 8.7 | |
6 days ago | 6 days ago | |
Go | Rust | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nix2container
-
Nix is a better Docker image builder than Docker's image builder
No discussion about Nix-built containers is complete with nix2container:
https://github.com/nlewo/nix2container
It is truly magical for handling large, multi-layered containers. Instead of building the container archives themselves and storing them in the nix store, it builds a JSON manifest that is consumed by a lightly patched version of skopeo that streams the layers directly to either your local container engine or the registry.
This means you never rebuild or reupload a container layer that is unchanged.
-
Way to get NVM working in CI/CD systems
- Container images are built with https://github.com/nlewo/nix2container instead of Nix's built-in docker tools, because nix2container allows configuration of layers and thus makes it easier to share layers between images and improve layer caching.
As for integrating it into our CI pipeline, this is pretty much CI system agnostic as all you have to do is run `nix build ...` inside the pipeline, generating a `result` directory or file as an artifact that, in the case of nix2container, can be pushed to your container image registry.
-
How do I create a docker image for postgres with nix?
dockerTools is the canonical way, but https://github.com/nlewo/nix2container seems to be gaining support as it's faster and doesn't use so much disk space while building.
-
We deploy 5X faster with warm Docker containers
> The key factor behind our decision was the realization that while Docker images are industry standard, moving around 100s of megabytes of images seems unnecessarily heavy-handed when we just need to synchronize a small change.
I think the culprit is more the GitHub Actions cache than Docker since it seems to be hard to get a clean cache management. I'm not sure about caching Docker image layers, but caching the Nix store with GitHub Actions is pretty complicated (not even sure it's possible): this means we have to download all required Nix store paths on each run, but i consider this is because of a GitHub Action cache limitation.
So, did you consider using another CI, which offers better caching mechanisms?
With a CI able to preserve the Nix store (Hydra[1] or Hercules[2] for instance), I think nix2container (author here) could also fit almost all of your requirements ("composability", reproducibility, isolation) and maybe provide better performances because it is able to split your application into several layers [2][3].
Note i'm pretty sure a lot of Docker CI also allows to efficiently build Docker images.
[1] https://hercules-ci.com/
[2] https://grahamc.com/blog/nix-and-layered-docker-images
[3] https://github.com/nlewo/nix2container/blob/85670cab354f7df6...
-
Launch HN: Depot (YC W23) – Fast Docker Images in the Cloud
FYI, the nix2container [1] project (author here) aims to speedup the standard Nix container workflow (dockerTools.buildImage) by basically skipping the tarball step: it directly streams non already pushed layers.
[1] https://github.com/nlewo/nix2container
-
Crafting container images without Dockerfiles
To get Rust incremental builds, did you consider using something such as crane https://github.com/ipetkov/crane ?
And regarding OCI images, i built nix2container (https://github.com/nlewo/nix2container) to speed up image build and push times.
-
Optimising Docker Layers for Better Caching with Nix (2018)
For a more modern iteration of that idea, check out https://github.com/nlewo/nix2container
It has all the benefits of OP but produces the images much faster, and with less on-disk usage.
-
Nixpacks takes a source directory and produces an OCI compliant image
I've been using nix2container[1] for awhile now. It looks like this depends on Docker, have you guys considered removing that dependency? It shouldn't be necessary to create an OCI compliant image with Nix.
[1]: https://github.com/nlewo/nix2container
-
Nixery – Docker images on the fly with Nix
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...
nixpacks
-
9 ways to improve how you ship software
Example with Nixpacks:
-
Multi-Worker Application on ARM Architecture
We have an upcoming nixpacks builder that should work on ARM/ARM64, but there are issues in the nixpacks codebase I'm still trying to sort out before that lands.
-
Using Nix with Dockerfiles
I think this is something the writer of the article would be delighted to find: https://github.com/railwayapp/nixpacks
-
[Media] Gitrun: Run any Git repository with one command
Yes, it builds the Dockerfile if it exists otherwise it uses nixpacks to create an image from source files for any language/framework. This image is then run using docker run .
- Show HN: IHP v1.0 (Batteries-included web framework built on Haskell and Nix)
-
We want to make Nix better
I think this is true for Nix in the deployment/ops space, where debugging a broken build can be very frustrating. Language improvements are going to be less useful for app developers, the Flake learning curve is not going to get better with a type system.
Perhaps something like heroku buildpaks (https://github.com/railwayapp/nixpacks ?) would help devs get on the Nix train.
-
A selfhosted Heroku clone on your Kubernetes cluster
Hey! Any plans on integrating nixpacks? I'm one of the core maintainers & would love to help you out. No worries if not.
- Nixpacks takes a source directory and produces an OCI compliant image
-
Deploying Strapi 4 to Railway
Uses NixPacks to build the images;
What are some alternatives?
naersk - Build Rust projects in Nix - no configuration, no code generation, no IFD, sandbox friendly.
sidekiq - Sidekiq worker on Render
crate2nix - rebuild only changed crates in CI with crate2nix and nix
web3.storage - DEPRECATED ⁂ The simple file storage service for IPFS & Filecoin
plane - A distributed system for running WebSocket services at scale.
cog - Containers for machine learning
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
heroku-deploy - A simple github action that dynamically deploys an app to heroku
cargo2nix - Granular builds of Rust projects for Nix
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
buildah - A tool that facilitates building OCI images.
engine - The Orchestration Engine To Deliver Self-Service Infrastructure Faster ⚡️