clair
kaniko
Our great sponsors
clair | kaniko | |
---|---|---|
21 | 49 | |
9,985 | 13,712 | |
0.9% | 1.8% | |
9.2 | 9.5 | |
6 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.
clair
-
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.
-
General Docker Troubleshooting, Best Practices & Where to Go From Here
Clair. Vulnerability Static Analysis for Containers.
-
Open source container scanning tool to find vulnerabilities and suggest best practice improvements?
https://github.com/quay/clair 9.4k stars, updated 17 hours ago
-
Postgres: The Graph Database You Didn't Know You Had
It scaled well compared to a naive graph abstraction implemented outside the database, but when performance wasn't great, it REALLY wasn't great. We ended up throwing it out in later versions to try and get more consistent performance.
I've since worked on SpiceDB[1] which takes the traditional design approach for graph databases and simply treating Postgres as triple-store and that scales far better. IME, if you need a graph, you probably want to use a database optimized for graph access patterns. Most general-purpose graph databases are just bags of optimizations for common traversals.
-
Implement DevSecOps to Secure your CI/CD pipeline
Open source: Trivy, Gryp and Clair are widely used open source tools for container scanning.
-
Sublime Music - A FLOSS desktop client for Subsonic API servers (Airsonic, Navidrome, Gonic, etc)
Testing the image with github.com/fullhunt/log4j-scan and https://github.com/quay/clair shows no vulnerabilities
-
Automatically tag your Docker images as vulnerable in ECR
Amazon Elastic Container Registry is a fully-managed Docker container registry. It makes it easy for developers to store and manage Docker images inside their AWS environment. ECR supports two types of image scanning. Enhanced image scanning requires an integration with Amazon Inspector. It will scan your repositories continuously. Basic image scanning will use the Common Vulnerabilities and Exposures (CVEs) database (open-source Clair) to find vulnerabilities in your images. You can trigger scans on image push or manually.
-
SaaS Startup Security 101 - A quick guide for building secure SaaS
Klair: Scan your containersJust like external dependencies can contain security flaws, container images also can contain outdated programs and dependencies subject to security issues. Klair is an open-source tool that can help you find outdated dependencies and security flaws in your docker images.
-
How to leverage image vulnerability scanning on AWS ECR using a fully automated solution
AWS Elastic Container Registry has been able to support the scanning of images for vulnerabilities using the open source project Clair for quite some time now. Clair is an open source project used for the static analysis of vulnerabilities in application containers (currently including OCI and Docker). Made available by AWS directly and implemented into ECR, it is a very useful feature to minimize the risk of using endangered software - and stay compliant. The scanning for vulnerabilities should be a good standard in any Dockerized scenario as public images and their heirs can contain many security risks (Top-ten-docker-images) - which might be overlooked while developing applications that are constantly changed and improved - and new versions of images are pushed to your ECR many times a day.
-
Hosting my own docker registry, any recommendations on UI and authentication service?
I use Quay and quite like it. It's a lot more flexible to deploy than Harbor. It has a web UI and connects to LDAP or OIDC. You can also add vulnerability scanning to it as well with Clair. The one downside is that it doesn't support a pull-through cache system like Harbor does (to my knowledge), though you can explicitly mirror containers from another source.
kaniko
-
Building Cages - Creating better DX for deploying Dockerfiles to AWS Nitro Enclaves
Kaniko for building the container images
-
Container and image vocabulary
kaniko
-
Schedule on Least Utilized Node
If you are using the docker socket just for building container images, you might want to look into kaniko. It doesn't use docker to build images. If you use the socket also for starting containers (we are actually doing that in our CI pipelines), you could think about limiting the pods Kubernetes schedules on a node (you can change the default of 110 using the kubelet config file).
-
You should use the OpenSSF Scorecard
It took less than 5 minutes to install. It quickly analysed the repo and identified easy ways to make the project more secure. Priya Wadhwa, Kaniko
-
Faster CI builds?
As for avoiding cargo rebuilding artifacts, make sure to use the same docker image, the same target dir and same workspace dir, every build. If you're using kaniko, it also does not preserve file timestamps (#1894) causing rebuilds.
-
Ask HN: How are you dealing with the M1/ARM migration?
According to Kaniko documentation [1], they don't really support cross-platform compilation. Do you solve that by having both amd64- and arm64-based CI/CD runners?
[1] https://github.com/GoogleContainerTools/kaniko#--customplatf...
-
Interaction between Docker, AMI and Ansible
Docker is a tool for building container images and running containers. Normally you'd compose a `Dockerfile` to configure an container image, include that `Dockerfile` at the root of an application repository, then use a CI/CD system to build and deploy that image on to a fleet of servers (possibly, but not necessarily, using Ansible!). You can use Ansible to build Docker images, but the idiomatic way - e.g. the least surprising, most common way - would be to use a `Dockerfile` and `docker` itself (or another builder such as [`Buildah`](https://buildah.io/) or [`kaniko`](https://github.com/GoogleContainerTools/kaniko)).
-
Deploy Node app to GCR without Docker?
Cloud Build builds the container image on either Container Registry (older) or Artifact Registry (newer). You can specify how Artifact Registry builds this container image. It could be with a Dockerfile, or directly from source code if you tell Artifact Registry to use pack, or it could even use something called kaniko (I never used it). Instead, if you'd rather build the container image on your computer, you could use whatever tool you want, as long as it produces an OCI-compliant container image.
-
Kubernetes for Startups: Practical Considerations for Your App
Build: Workloads need to be containerized. That leads to long build times, especially if there is no caching possible/enabled for the build. A local build might be just a hot reload, but these can take many minutes with the container build step included. Please use podman, kaniko, or similar over docker for builds.
-
📺 Certified Kubernetes Administrator (CKA) training from CBT Nuggets 👨🏻💻👩🏻💻
Kaniko - build container images directly in Kubernetes clusters
What are some alternatives?
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
podman - Podman: A tool for managing OCI containers and pods.
buildah - A tool that facilitates building OCI images.
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
jib - 🏗 Build container images for your Java applications.
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
grype - A vulnerability scanner for container images and filesystems
skopeo - Work with remote images registries - retrieving information, images, signing content
source-to-image - A tool for building artifacts from source and injecting into container images
ko - Build and deploy Go applications
pack - CLI for building apps using Cloud Native Buildpacks
docker-install - Docker installation script