Files
falco/docker
Daniel Wright 2e7a0b026f feat: add jq and curl to falco-no-driver docker image
To supoprt the use of outputs that are documented in the falco
examples (e.g. jq piped to curl) I would like to propose including
these tools in the falco-no-driver image. They add a very minimal
size and dependency to the image but would make things a lot easier
for users getting started.

Closes #2580

Signed-off-by: Daniel Wright <danielwright@bitgo.com>
2023-05-31 13:21:31 +02:00
..
2019-04-26 12:24:15 -07:00

Falco Dockerfiles

This directory contains various ways to package Falco as a container and related tools.

Currently Supported Images

Name Directory Description
falcosecurity/falco:latest, falcosecurity/falco:tag, falcosecurity/falco:master docker/falco Falco (DEB built from git tag or from the master) with all the building toolchain.
not yet published (experimental) docker/ubi Falco (built from RedHat's UBI base image) with the building toolchain.
falcosecurity/falco-driver-loader:latest, falcosecurity/falco-driver-loader:tag, falcosecurity/falco-driver-loader:master docker/driver-loader falco-driver-loader as entrypoint with the building toolchain.
falcosecurity/falco-no-driver:latest, falcosecurity/falco-no-driver:tag,falcosecurity/falco-no-driver:master docker/no-driver Falco (TGZ built from git tag or from the master) without the building toolchain.
falcosecurity/falco-builder:latest docker/builder The complete build tool chain for compiling Falco from source. See the documentation for more details on building from source. Used to build Falco (CI).
falcosecurity/falco-tester:latest docker/tester Container image for running the Falco test suite. Used to run Falco integration tests (CI).
not to be published docker/local Built on-the-fly and used by falco-tester.

Note: falco-builder, falco-tester (and the docker/local image that it's built on the fly) are not integrated into the release process because they are development and CI tools that need to be manually pushed only when updated.