go-containerregistry
roadmap
go-containerregistry | roadmap | |
---|---|---|
17 | 49 | |
2,962 | 1,447 | |
1.2% | 1.2% | |
6.8 | 2.6 | |
5 days ago | 2 months ago | |
Go | ||
Apache License 2.0 | Creative Commons Zero v1.0 Universal |
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
-
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
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?
Look at using tools like skopeo or crane
-
Containerd... Do I use Docker to build the container image? I miss the Docker Shim
Pretty much any tool works: docker, podman, kaniko, crane(if you're brave), ko... list goes on.
roadmap
- Docker considering flatpak and snap apps for Linux (please upvote)
-
Apple unveils M3, M3 Pro, and M3 Max, the most advanced chips for a PC
x86-64 containers?
https://github.com/docker/roadmap/issues/384 is still open. :(
-
Debugging Slim Containers: A quick tutorial using the "Docker Labs Debug Tools" extension
Request features or give feedback: https://github.com/docker/roadmap/issues/524
-
"The docker container stop command is deprecated" - is this true?
Nothing in the road map [Github] returned by searching 'stop'.
-
How do I get real client IP inside docker container for logging to the database
Further reading online revealed that host network mode is not available for swarm started with docker stack deploy. (Possible related open issue: github link).
-
Serious Question: why use Docker Desktop? (from a Linux user)
Single-click k8s install. Extensions. Init. And there are people who just prefer an app-based experience for their own reasons - I think it was the most "upvoted" request ever on their public roadmap.
-
Ask HN: Is MacBook Pro 14 M1 16/512 still a great choice?
In case you need to run x86 containers: Docker has Rosetta support now but it's buggy.
https://github.com/docker/roadmap/issues/384
Without Rosetta it uses relatively slow Qemu emulation.
-
Docker's deleting Open Source images and here's what you need to know
https://github.com/docker/roadmap/issues/44
So, at the moment, any public organization images are doomed to be lost, if they won't pay.
-
How's the M2 Max for Docker development?
I've been watching this GitHub issue for damn near 3 years. Filesystem performance is pretty bad, depending on what you're doing. I had to kludge together workarounds to my DX at my last role where we used Docker for development. It was really, really painful and distracting.
-
Launch HN: Moonrepo (YC W23) – Open-source build system
[2] https://github.com/docker/roadmap/issues/7
What are some alternatives?
skopeo - Work with remote images registries - retrieving information, images, signing content
podman-compose - a script to run docker-compose.yml using podman
regclient - Docker and OCI Registry Client in Go and tooling using those libraries.
microk8s - MicroK8s is a small, fast, single-package Kubernetes for datacenters and the edge.
container-diff - container-diff: Diff your Docker containers
multipass - Multipass orchestrates virtual Ubuntu instances
image-spec - OCI Image Format
swarmkit - A toolkit for orchestrating distributed systems at any scale. It includes primitives for node discovery, raft-based consensus, task scheduling and more.
gcr-cleaner - Delete untagged image refs in Google Container Registry or Artifact Registry
rancher - Complete container management platform
docker-tools - This is a repo to house some common tools for our various docker repos.
toolbox - The Docker Toolbox