Last changed
Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.
Sign UpA minimal, wolfi-based image for falco-no-driver. This streamlined variant of Falco designed for real-time security monitoring on Linux, replaces the traditional kernel module with eBPF technology, thus enhancing portability in containerized environments.
Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.
This image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard registry.
The primary distinction between falco, and falco-no-driver (i.e this image), lies in their approach to monitoring system calls.
Falco requires a kernel-specific module to hook into the system an monitor system calls.
In contrast, falco-no-driver does not depend on a kernel-specific module, instead leveraging eBPF (modern-bpf driver). This eliminates the need for loading sepatate kernel modules and makes the image more portable, between environments.
When we talk about falco-no-driver, this means no kernel drivers. falco-no-driver is bundled with the modern-bpf driver itself. This can be confusing and is worth clarifying.
If you are intending on testing this image locally, note that falco does not run on macOS. If you attempt to run the image it will fail to launch. See the following falco documentation, where they recommend setting up a linux VM.
Please refer to the upstream documentation for instructions on how to configure and run falco-no-driver. The below examples are intended as demonstrating how to substitute with the chainguard image, and are not comprehensive.
The deployment of Falco in a Kubernetes cluster is managed through a Helm chart. Documentation on this helm chart is available here
To install falco-no-driver image supporting modern bpf probe,
If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.
Chainguard Images are a collection of container images designed for security and minimalism.
Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.
The main features of Chainguard Images include:
-dev
VariantsAs mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev
variant which does include a shell and package manager.
Although the -dev
image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev
variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.
That being said, it’s worth noting that -dev
variants of Chainguard Images are completely fine to run in production environments. After all, the -dev
variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.
To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.
Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:
( GPL-2.0-or-later
Apache-2.0
BSD-2-Clause
GCC-exception-3.1
GPL-2.0-only
GPL-3.0-or-later
LGPL-2.1-or-later
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementA FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.