Go-containerregistry Alternatives

go-containerregistry reviews and mentions

• A gopher’s journey to the center of container images
  5 projects | dev.to | 23 Nov 2023

  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
  3 projects | /r/gitlab | 24 Apr 2023

  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
  3 projects | news.ycombinator.com | 24 Mar 2023

  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
  1 project | /r/kubernetes | 23 Mar 2023

  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.
  2 projects | /r/DataHoarder | 15 Mar 2023
• FYI: Docker is deleting Open Source organisations
  9 projects | /r/selfhosted | 15 Mar 2023

  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
  23 projects | news.ycombinator.com | 15 Mar 2023

  https://github.com/google/go-containerregistry/tree/main/cmd...

  It was recommended in this article:

• Crafting container images without Dockerfiles
  20 projects | news.ycombinator.com | 6 Feb 2023

  This is one of my absolute favorite topics. Pardon me while I rant and self-promote :D

  Dockerfiles are great for flexibility, and have been a critical contributor to the adoption of Docker containers. It's very easy to take a base image, add a thing to it, and publish your version.

  Unfortunately Dockerfiles are also full of gotchas and opaque cargo-culted best practices to avoid them. Being an open-ended execution environment, it's basically impossible to tell even during the build what's being added to the image, which has downstream implications for anybody trying to get an SBOM from the image for example.

  Instead, I contribute to a number of tools to build and manage images without Dockerfiles. Each of them are less featureful than Dockerfiles, but being more constrained in what they can do, you can get a lot more visibility into what they're doing, since they're not able to do "whatever the user wants".

  1. https://github.com/google/go-containerregistry is a Go module to interact with images in the registry and in tarballs and layouts, in the local docker daemon. You can append layers, squash layers, modify metadata, etc.

  2. crane is a CLI that uses the above (in the same repo) to make many of the same modifications from the commandline. `crane append` for instance adds a layer containing some contents to an image, entirely in the registry, without even pulling the base image.

  3. ko (https://ko.build) is a tool to build Go applications into images without Dockerfiles or Docker at all. It runs `go build`, appends that binary on top of a base image, and pushes it directly to the registry. It generates an SBOM declaring what Go modules went into the app it put into the image, since that's all it can do.

  4. apko (https://apko.dev) is a tool to assemble an image from pre-built apks, without Docker. It's capable of producing "distroless" images easily with config in YAML. It generates an SBOM declaring exactly what apks it put in the image, since that's all it can do.

  Bazel's rules_docker is another contender in the space, and GCP's distroless images use it to place Debian .debs into an image. Apko is its spiritual successor, and uses YAML instead of Bazel's own config language, which makes it a lot easier to adopt and use (IMO), with all of the same benefits.

  I'm excited to see more folks realizing that Dockerfiles aren't always necessary, and can sometimes make your life harder. I'm extra excited to see more tools and tutorials digging into the details of how container images work, and preaching the gospel that they can be built and modified using existing tooling and relatively simple libraries. Excellent article!

• 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?
  3 projects | /r/kubernetes | 13 Sep 2022

  Look at using tools like skopeo or crane

• Containerd... Do I use Docker to build the container image? I miss the Docker Shim
  5 projects | /r/kubernetes | 25 Jun 2022

  Pretty much any tool works: docker, podman, kaniko, crane(if you're brave), ko... list goes on.

• A note from our sponsor - InfluxDB
  www.influxdata.com | 18 Apr 2024

  Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →