go-containerregistry
Go library and CLIs for working with container registries (by google)
crane
A Nix library for building cargo projects. Never build twice thanks to incremental artifact caching. (by ipetkov)
| go-containerregistry | crane | |
|---|---|---|
| 18 | 15 | |
| 3,423 | 1,099 | |
| 1.5% | 2.9% | |
| 6.8 | 9.0 | |
| 8 days ago | 12 days ago | |
| Go | Nix | |
| Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
go-containerregistry
Posts with mentions or reviews of go-containerregistry.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-23.
- Crane: Tool for interacting with remote images and registries
-
A gopher’s journey to the center of container images
I also explored another module, go-containerregistry, in order to build images without root privileges. The approach is completely different, and we can manipulate each component of the container image separately. This can present an advantage, if you're looking for a way to fine tune things.
-
Skip build if "${CI_REGISTRY_IMAGE}:${CI_COMMIT_SHORT_SHA}" exists on container registry
Use crane ls in a different job to check the tags in the registry. Create an artifact from its output that you evaluate in your kaniko job to check if the build should run or not.
-
Docker: We’re No Longer Sunsetting the Free Team Plan
Multi-arch builds are easy to "transfer" IMHO
crane cp docker.io/openfaas/gateway:0.10.0 ghcr.io/openfaas/gateway:0.10.0
If you've not used it yet - do take a look. Crane doesn't pull the images into a local Docker library for re-tagging and re-pushing.
https://github.com/google/go-containerregistry/blob/main/cmd...
-
Weekly: This Week I Learned (TWIL?) thread
crane - tool to copy images from one repo to another - https://github.com/google/go-containerregistry/blob/main/cmd/crane/doc/crane.md
- Dockerhub to (likely?) delete a lot of organizations.
-
FYI: Docker is deleting Open Source organisations
pretty sure the crane being referred by alex is this one: https://github.com/google/go-containerregistry/tree/main/cmd/crane
-
Docker's deleting Open Source images and here's what you need to know
https://github.com/google/go-containerregistry/tree/main/cmd...
It was recommended in this article:
- Crafting container images without Dockerfiles
-
ImagePullPolicy: IfNotPresent - (image doesn’t exist in repo) - Is it possible to pull the micro service image from an EKS node and then push to repo?
Look at using tools like skopeo or crane
crane
Posts with mentions or reviews of crane.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-05-13.
-
Posta: Building a Social Blogging Backend with SurrealDB, Nix, and Nushell
While doing research for these projects I came across some small bugs in another project. I made the fixes and opened some PRs which were accepted.
-
Debian's approach to Rust – Dependency handling (2022)
https://github.com/ipetkov/crane makes integrating rust and nix incredibly easy
-
Embrace the Power of Nix for Your Python + Rust Workflow
We use Crane, a Nix library for building Cargo projects. One of Crane’s standout features is incremental artifact caching, which ensures you never build the same artifact twice. This greatly speeds up the build process and reduces redundant work.
- Can rustc generate identical binaries, with the same hash, from the same souce code?
- Transitioning to Rust as a company
-
Help with building a 32bit library with cargo
i would also recommend using crane or naersk since iirc rustPlaform.buildRustPackage can mangle some of these options (or maybe i just did something wrong lol)
-
Better support of Docker layer caching in Cargo
Notably crane is doing what cargo-chef is doing for Nix.
-
20 Years of Nix
I don't think it's very valid to compare the two. It is a little bit just to compare the experiences using them bit they aren't meant to solve the same set of issues. In fact, they are better together in my experience. I use nix to manage my terraform configurations with a lot of success. It reduces my boilerplate and helps me build abstractions on top of HCL.
If you ever decide to take a stab at nix again, consider looking at https://github.com/ipetkov/crane and using flakes. I've got it down to the point that I can get a new rust project set up with nix in about 30 seconds with linting, package building, and test running all in the checks
-
Has anyone packaged Rust programs as nix packages?
Take a look at Crane, though it is squarely aimed at non-beginners. If you want to submit whatever you're packaging to nixpkgs and not just for personal use, you can't use crane, though.
-
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.
What are some alternatives?
When comparing go-containerregistry and crane you can also consider the following projects:
skopeo - Work with remote images registries - retrieving information, images, signing content
naersk - Build Rust projects in Nix - no configuration, no code generation, no IFD, sandbox friendly.
image-spec - OCI Image Format
cargo-auditable - Make production Rust binaries auditable
regclient - Docker and OCI Registry Client in Go and tooling using those libraries.
api - 🎭 API