go-containerregistry
kubevirt
go-containerregistry | kubevirt | |
---|---|---|
17 | 50 | |
2,962 | 5,092 | |
1.2% | 1.5% | |
6.8 | 10.0 | |
6 days ago | 5 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
kubevirt
-
Kubernetes For The Sysadmin - Enter KubeVirt
First, download virtctl for ARM: https://github.com/kubevirt/kubevirt/releases/tag/v1.1.0-alpha.0
-
KubeVirt v1.0 has landed! This release demonstrates the accomplishments of the community and user adoption over the years
The full list of changes can be found in the Release notes. There are performance and scalability benchmarks published for the v1.0 release.
- What is the status of Red Hat Enterprise Virtualization and oVirt?
-
Proxmox, CEPH and kubernetes
If you're happy with k8s and longhorn, why add Proxmox as another layer underneath? Consider kubevirt ?
-
Kubernetes for temporary VM?
Have you looked at http://kubevirt.io/ ?
-
How does your company roll out code?
If the answer to "how do you run VMs" is "Kubernetes does it" then its about https://kubevirt.io/
-
Docker's deleting Open Source images and here's what you need to know
We are even using Docker Hub to store and distribute VM images...
https://github.com/kubevirt/kubevirt/blob/main/containerimag...
-
Blog: KWOK: Kubernetes WithOut Kubelet
Docker Desktop runs dockerd in a Linux VM with Apple's hypervisor framework. You can also run containers in a Linux VM with Parallels or VMware Fusion hypervisors. But you can't run VMs inside those VMs as it stands today. This works fine on Intel Macs which means you can't experiment and use KVM - one of the killer features of Linux and things like https://kubevirt.io/
-
Docker + portainer vs k8. EILI5
Proxmox VE can run VMs and LXC containers (see my comment below on LXC). Kubernetes can run OCI containers, but there's also KubeVirt for running VMs.
-
Live Switching Pods to another Node on Resource Limits
Another option would be something like KubeVirt but that is a different use case where you are actually running a VM in a container for hard-to-containerize workloads.
What are some alternatives?
skopeo - Work with remote images registries - retrieving information, images, signing content
harvester - Open source hyperconverged infrastructure (HCI) software
regclient - Docker and OCI Registry Client in Go and tooling using those libraries.
firecracker-containerd - firecracker-containerd enables containerd to manage containers as Firecracker microVMs
container-diff - container-diff: Diff your Docker containers
kata-containers - Kata Containers is an open source project and community working to build a standard implementation of lightweight Virtual Machines (VMs) that feel and perform like containers, but provide the workload isolation and security advantages of VMs. https://katacontainers.io/
image-spec - OCI Image Format
k3s - Lightweight Kubernetes
gcr-cleaner - Delete untagged image refs in Google Container Registry or Artifact Registry
lxd - Powerful system container and virtual machine manager [Moved to: https://github.com/canonical/lxd]
docker-tools - This is a repo to house some common tools for our various docker repos.
cloud-hypervisor - A Virtual Machine Monitor for modern Cloud workloads. Features include CPU, memory and device hotplug, support for running Windows and Linux guests, device offload with vhost-user and a minimal compact footprint. Written in Rust with a strong focus on security.