grype
apko
grype | apko | |
---|---|---|
56 | 14 | |
7,885 | 1,078 | |
4.8% | 6.8% | |
9.5 | 9.4 | |
2 days ago | 4 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.
grype
-
Introduction to the Kubernetes ecosystem
Trivy Operator : A simple and comprehensive vulnerability scanner for containers and other artifacts. It detects vulnerabilities of OS packages (Alpine, Debian, CentOS, etc.) and application dependencies (pip, npm, yarn, composer, etc.) (Alternatives : Grype, Snyk, Clair, Anchore, Twistlock)
- Suas imagens de container não estão seguras!
-
I looked through attacks in my access logs. Here's what I found
Besides pointing pentester tools like metasploit at yourself, there are some nice scanners out there.
https://github.com/quay/clair
https://github.com/anchore/grype/
-
Distroless images using melange and apko
Using Grype:
-
Scanning and remediating vulnerabilities with Grype
In the lab to follow, we'll see how vulnerability scanning can be conveniently achieved with Grype and how various systematic techniques can be applied to start securing our microservices at the container image level.
-
Understanding Container Security
Scanning your container images for vulnerabilities is a good approach. But this scanning is not one time job, it should be done regularly (weekly, monthly, etc.) You need to follow vulnerability reports and fix all of the vulnerabilities as soon as possible. I recommend some open-source tools that could be useful: Trivy, Docker-Bench, Grype.
-
An Overview of Kubernetes Security Projects at KubeCon Europe 2023
Grype is another popular open source tool from Anchore. Working with SBOM files, Grype scans container images and filesystems for vulnerabilities. Grype supports different output formats for vulnerabilities and custom templates for output.
-
Best vulnerability scanner for DevOps
Grype (https://github.com/anchore/grype)
-
Security docker app
Grype will allow you to scan a container to see if you have any vulnerable packages.
-
Open source container scanning tool to find vulnerabilities and suggest best practice improvements?
https://github.com/anchore/grype 5.6k stars, updated 3 days ago
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:
What are some alternatives?
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
distroless - 🥑 Language focused docker images, minus the operating system.
anchore-engine - A service that analyzes docker images and scans for vulnerabilities
docker-pushmi-pullyu - Copy Docker images directly to a remote host without using Docker Hub or a hosted registry.
clair - Vulnerability Static Analysis for Containers
containerd - An open and reliable container runtime
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
melange - build APKs from source code
opencve - CVE Alerting Platform
osv-scanner - Vulnerability scanner written in Go which uses the data provided by https://osv.dev
falco - Cloud Native Runtime Security
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...