apko
cargo-chef
apko | cargo-chef | |
---|---|---|
14 | 18 | |
1,090 | 1,568 | |
3.2% | - | |
9.4 | 7.0 | |
5 days ago | 12 days ago | |
Go | Rust | |
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:
cargo-chef
-
Transitioning to Rust as a company
CI time. Do you want to micromanage your own docker images for all your CI? Great! If not, yes you do. In fact, you want to manage a docker image to build a docker image to use for CI. Use cargo-chef to prepare a build image with your dependencies pre-built if you want to do fine-grained build/test pipelines. Oh also, there's no jUnit test report generation, that was killed off today. (YES, SORRY, I'm still salty.)
-
Rust and Next.js everywhere?
Have you looked at cargo-chef? It supposedly speeds up compilation times if you're using Docker.
-
Exploring the problem of faster Cargo Docker builds
A tool already exists for this called Cargo-chef, and it works extremely well.
-
Deploying Rust APIs | What Is Your Favorite Method?
At work I've use Dockerfile and cargo-chef to improve build times. You can also look into buildkit cache mounts, but this approach is rarely super effective on hosted CI because they start from scratch on most runs. In the context of Rust specifically you may also see the target directory reflect unbounded data growth if it's reused over and over across revisions. because cargo by default won't expire older intermediate artifacts. Cargo-sweep can help with that but I wouldn't pursue this in a CI effort. This will affect both "native" builds and buildkit cache mounts if you're persisting the target directory.
-
How to write a GitHub Action in Rust
We create an empty Rust binary with cargo new, this is a simple way to get Docker layer caching to work. For a more robust solution, you may want to check out cargo-chef.
-
Crafting container images without Dockerfiles
If this ends up being a cleaner/easier way to having to workaround super expensive rebuilds for Rust given cache + deps compared to this https://github.com/LukeMathWalker/cargo-chef , reading this thread will have been a huge win for me (and hopefully others).
Whether introducing Bazel is easier/worth it, subjective I guess.
-
Is it possible to get fast Rust compiles in a Docker container?
I did a talk (slides here) about this a few years ago, it took a bit of work to get the build caching working with cargo. As others have pointed out, there is now cargo chef to solve this problem so you probably don't have to deal with the issues I saw, but I thought it still might be helpful context.
-
Faster CI builds for Rust with pre-baked builder images and sccache
I'm curious if you've tried out cargo-chef, I've had some decent improvements with it but I wonder how it stacks up to the sccache approach (don't have the time to try it out myself right now).
-
2 years of fiddling with Rust – critical thoughts
for CI have you tried to use buildkit persistent runners with caching + https://github.com/LukeMathWalker/cargo-chef ?
-
How to speed up the Rust compiler in July 2022
If you're deploying Rust with Docker I can tell you that cargo-chef is invaluable. With zero work it caches the dependency fetch and compilation steps. Most of the time the ens Docker deploy is closer to an incremental compile than full.
What are some alternatives?
distroless - 🥑 Language focused docker images, minus the operating system.
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
docker-pushmi-pullyu - Copy Docker images directly to a remote host without using Docker Hub or a hosted registry.
rules_rust - Rust rules for Bazel
containerd - An open and reliable container runtime
mold - Mold: A Modern Linker 🦠
melange - build APKs from source code
cargo-sweep - A cargo subcommand for cleaning up unused build files generated by Cargo
osv-scanner - Vulnerability scanner written in Go which uses the data provided by https://osv.dev
bloom - The simplest way to de-Google your life and business: Inbox, Calendar, Files, Contacts & much more
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
monadium - A platform with the purpose to teach Rust web development to people with no prior experience of programming