apko
podman
apko | podman | |
---|---|---|
14 | 361 | |
1,090 | 22,019 | |
3.2% | 1.3% | |
9.4 | 10.0 | |
5 days ago | 7 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.
apko
-
Distroless images using melange and apko
apko allows us to build OCI container images from .apk packages.
- Build OCI images from APK packages directly without Dockerfile
-
Docker Is Four Things
We have built something very similar to what you are describing: https://github.com/chainguard-dev/apko
- Apko: APK-based OCI image builder
-
Tool to build Docker images
apko
-
An Overview of Kubernetes Security Projects at KubeCon Europe 2023
Chainguard also appears to have several open source projects.The most popular one is apko, used for building OCI images from APK packages.
-
aws-cli v2: how much smaller can it get? Answer: a lot smaller :)
Once those are done, I just need to build aws-cli package, put those APK files in a final image with Chainguard's apko.
-
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!
-
Vulnerability scanner written in Go that uses osv.dev data
Depends exactly what you're trying to create it for. I advocate for doing it during the build process rather than as a step after.
We open sourced a few tools that do it automatically for containers:
https://github.com/chainguard-dev/apko
https://github.com/chainguard-dev/melange
-
Apko: A Better Way To Build Containers?
apko takes apk packages and builds them into OCI images (aka Docker images). Sounds quite simple, because it is:
podman
-
How I ended up using Colima for Docker on Apple Silicon
A lot of well-known Docker alternatives emerged at this point, the most commonly recommended of which must be Podman (along with Podman Desktop). This is what I use on my Windows machines, and this was the first solution that I tried on the Macbook as well.
-
Podman 5.0 has been released
Example of why: https://github.com/containers/podman/issues/5102#issuecommen...
-
Exploring 5 Docker Alternatives: Containerization Choices for 2024
Podman
- Podman 5.0.0: final release candidate
-
A Gentle Introduction to Containerization and Docker
Even though we will focus on Docker for this article, I wanted to mention that there are more container creation and management tools such as Podman, Rkt, and so on.
-
A Journey to Find an Ultimate Development Environment
By using containerization, the application will always have the same configuration that is used in the development environment and production environment. There is no more "It works on my machine". Some examples of containerization technologies are Docker and Podman.
-
Anatomy of Docker
Podman Documentation. Podman is a daemonless container engine for developing, managing, and running OCI Containers on your Linux System.
-
Exploring Podman: A More Secure Docker Alternative
AFAIK podman either already supports pods in quadlet container files, or will in the near future. https://github.com/containers/podman/pull/20762
-
Podman Desktop 1.6 released: Even more Kubernetes and Containers features
Podman as a devcontainers engine doesn't currently work if you use devcontainer features [1] or (and this sounds like you're issue) if you use WSL2.
I haven't submitted the WSL2 issue to the Podman team yet. If you get to it before I do, can you like it here?
https://github.com/containers/podman/issues/18691#issuecomme...
-
Oracle data base
You can also use their Oracle Linux Docker images with the database preinstalled using either Podman or Docker. Just make absolutely sure you are downloading something you are licensed to use, because it seems really easy to accidentally infringe copyright via this method.
What are some alternatives?
distroless - 🥑 Language focused docker images, minus the operating system.
Portainer - Making Docker and Kubernetes management easy.
docker-pushmi-pullyu - Copy Docker images directly to a remote host without using Docker Hub or a hosted registry.
lima - Linux virtual machines, with a focus on running containers
containerd - An open and reliable container runtime
kaniko - Build Container Images In Kubernetes
melange - build APKs from source code
rancher - Complete container management platform
osv-scanner - Vulnerability scanner written in Go which uses the data provided by https://osv.dev
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...