skopeo
dockcheck
Our great sponsors
skopeo | dockcheck | |
---|---|---|
22 | 33 | |
7,364 | 709 | |
3.9% | - | |
9.0 | 8.8 | |
3 days ago | 2 days ago | |
Go | Shell | |
Apache License 2.0 | GNU General Public License v3.0 only |
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.
skopeo
-
A better, faster approach to downloading docker images without docker-pull: Skopeo
I decided to go searching for an alternative means to pull a docker image. In my search I discovered Skopeo, an alternative method to download Docker images that proved to be surprisingly effective. It not only downloaded the image faster, it also allowed me to save my image in a tar file, which means you can pull an image on one system and share that image to another system, loading it easily to docker instance on that system. This can be very beneficial if you have multiple systems and don't want to download an image multiple times.
-
[OC] Update: dockcheck - Checking updates for docker images without pulling - automatically update containers by choice.
But I'd suggest looking into if it's solved by other tools already, like regclient/regclient and their regsync features or something like containers/skopeo.
-
Wrapping Go CLI tools in another CLI?
Have a use case where we have a CLI (built with cobra) for our dev teams which can execute common tasks. One of those tasks we want to implement is to copy docker images from the internet to our internal registry. A tool such as skopeo can do this and much more. Instead of essentially re-writing the functionality directly into our CLI we'd like to embed it. This would also negate the need for the dev teams to manage multiple CLI tools.
-
Rails on Docker · Fly
Self hoisting here, I put this together to make it easier to generate single (extra) layer docker images without needing a docker agent, capabilities, chroot, etc: https://github.com/andrewbaxter/dinker
Caveat: it doesn't work on Fly.io. They seem to be having some issue with OCI manifests: https://github.com/containers/skopeo/issues/1881 . They're also having issues with new docker versions pushing from CI: https://community.fly.io/t/deploying-to-fly-via-github-actio... ... the timing of this post seems weird.
FWIW the article says
> create a Docker image, also known as an OCI image
I don't think this is quite right. From my investigation, Docker and OCI images are basically content addressed trees, starting with a root manifest that points to other files and their hashes (root -> images -> layers -> layer configs + files). The OCI manifests and configs are separate to Docker manifests and configs and basically Docker will support both side by side.
-
How are you building docker images for Apple M1?
skopeo is another tool worth looking into. we've started deploying amd and arm nodes into our k8s clusters, and this tool was incredibly easy to build around for getting multi-arch images into our container registry.
-
Get list of image architectures
I would use skopeo, the tool is quite handy for working with remote images. https://github.com/containers/skopeo
-
Implement DevSecOps to Secure your CI/CD pipeline
Using distroless images not only reduces the size of the container image it also reduces the surface attack. The need for container image signing is because even with the distroless images there is a chance of facing some security threats such as receiving a malicious image. We can use cosign or skopeo for container signing and verifying. You can read more about securing containers with Cosign and Distroless Images in this blog.
-
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
-
Monitoring image updates when not using :latest!
You could try some commandline tool like skopeo to fetch the image tags regularly and do some shell magic to notify you on any change you want
-
Containers without Docker (podman, buildah, and skopeo)
This is what Podman, an open-source daemonless and rootless container engine, was developed with in mind. Podman runs using the runC container runtime process, directly on the Linux kernel, and launches containers and pods as child processes. In addition, it was developed for the Docker developer, with most commands and syntax seamlessly mirroring Docker's. Buildah, an image builder, and Skopeo, the image utility tool, are both complimentary to Podman as well, and extend the range of operations able to be performed.
dockcheck
- Should I be using a unified Docker-Compose.yml?
-
PSA - Run "docker image prune" once in a while.
As someone who knows just enough about Docker to be able to scratch together a docker-compose.yml every now and again only to promptly forget all the commands I need to ever maintain them going forward, I'm eternally grateful that dockcheck.sh prompts me to do this as a final step whenever I run it.
-
How to safely update the docker to latest?
I’m a simple man. I upgrade everything via dockcheck, verify that everything still works, and if not restore from backup!
-
Portainer kind of screwed me after updating a container -- Any other alternatives to managing your containers?
And I've personally made a script to selectively auto-update containers, or just check status. With the option to filter or exclude specific containers. Find the project here: mag37/dockcheck
-
Update containers/images to latest version in Docker Desktop (windows)
To "mass-check and mass-update" containers from the commandline, dockcheck is very light and useful. A simple dockcheck.sh -a -p for example would check all deployed containers for image updates and if there are any, pull them, then restart the container and at the end, cleanup unused images to free up diskspace. There is also a version with a web interface, DCW.
- Docker container update notifications
- new to Alma, a bunch of questions (mostly aimed towards podman)
- Is there a centralized Docker Container Management for updating containers?
-
Jellyfin: Critical remote code execution vulnerability in versions before 10.8.10
I haven’t gone the watchtower route, since I’d prefer to review changes myself (or let’s be honest - others’ reactions to the changes). Instead. I’ve been using a combo of diun and dockcheck (https://github.com/mag37/dockcheck ). Diun lets me know when containers have changed and dockcheck lets me cherry pick what I upgrade.
-
Watchtower: understand which containers have problem from the log
If you want to update images, try dockcheck or DCW.
What are some alternatives?
go-containerregistry - Go library and CLIs for working with container registries
watchtower - A process for automating Docker container base image updates.
kaniko - Build Container Images In Kubernetes
dockcheck-web - A webpage showing available image updates for your running containers.
dive - A tool for exploring each layer in a docker image
regclient - Docker and OCI Registry Client in Go and tooling using those libraries.
sinker - A tool to sync images from one container registry to another
portainer-ce-without-annoying - A drop-in replacement for portainer/portainer-ce, without annoying UI elements or tracking script
jib - 🏗 Build container images for your Java applications.
ctop - Top-like interface for container metrics
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
apprise - Apprise - Push Notifications that work with just about every platform!