go-containerregistry
Diun
Our great sponsors
go-containerregistry | Diun | |
---|---|---|
17 | 72 | |
2,917 | 2,522 | |
2.6% | - | |
7.3 | 9.0 | |
6 days ago | 5 days ago | |
Go | Go | |
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.
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...
- 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.
-
`COPY --chmod` reduced the size of my container image by 35%
There's also (another shameless plug) crane append which simply adds the contents of a tar to an existing base image directly in the registry: https://github.com/google/go-containerregistry/blob/main/cmd/crane/doc/crane_append.md
Diun
- Is there a tool to monitor container images version locally and notify if there are updates?
-
PSA - Run "docker image prune" once in a while.
Thanks, I used to use it. I moved to using diun to just notify of updates but not apply them though.
-
Update containers/images to latest version in Docker Desktop (windows)
Similar to Watchtower but without the option to auto-update containers, just notifying is diun. But imo it does that better and more reliable than Watchtower does. You can get notified by Email, Discord, Pushover, Telegram and many more options.
-
Seatch for apps updates notifier app
If your apps are container images, then there are tools like diun, watchtower and whatsupdocker, those can watch the image repository (like Docker Hub) and notify you if a new/updated image has been found. Some can even download and auto-update for you, but that comes at some risk of course.
-
Is there a centralized Docker Container Management for updating containers?
diun is very similar to that, but it doesnt auto-update, just notifies but does that very well imo.
-
Docker Swarm: automatically update service when new image is released
I use https://crazymax.dev/diun/ to send notifications of new images. I also hook it into webbooks with CI for mirroring images, but you should be able to use something like portainer webhooks to auto pull images.
-
Docker container update notifier - watchCat
Seems very similar to diun but i like the feature to put containers into groups.
-
Watchtower: understand which containers have problem from the log
If you want notifications on new image updates, try diun.
-
Release Watcher with UI
Argus sounds like it will do a lot/most/all of what you're looking for. Super easy to set up with Docker. I had it running for quite a while but just moved everything to either Github release notification emails or diun (docker image update notifier). No real reason for my switch besides laziness/familiarity. Check it out!
-
What to use with Docker?
I would instead use DIUN, which will notify you when there are updates so you can make your own decisions: https://github.com/crazy-max/diun
What are some alternatives?
watchtower - A process for automating Docker container base image updates.
skopeo - Work with remote images registries - retrieving information, images, signing content
whats-up-docker - What's up Docker ( aka WUD ) gets you notified when a new version of your Docker Container is available.
docker-socket-proxy - Proxy over your Docker socket to restrict which requests it accepts
regclient - Docker and OCI Registry Client in Go and tooling using those libraries.
discord-image-downloader-go - A simple tool which downloads pictures posted in discord channels of your choice to a local folder.
shepherd - Docker swarm service for automatically updating your services whenever their image is refreshed
swarm-cronjob - Create jobs on a time-based schedule on Docker Swarm
notify - File system event notification library on steroids.
renovate - Universal dependency automation tool.
Cryptomator - Multi-platform transparent client-side encryption of your files in the cloud
Sandboxie - Sandboxie Plus & Classic