Files
falco/docker
Leonardo Grasso 53a1be66b0 chore(docker/builder): remove never used MINIMAL_BUILD option
The option was added but could not work since MINIMAL_BUILD is not declared in this scope (also not currently needed).
Furthermore, it never took effect since the builder image was never built and pushed. For the same reason, we have not noticed it until now.

Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
2021-05-21 10:24:08 +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.
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).
to not 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.