mirror of
https://github.com/falcosecurity/falco.git
synced 2025-10-22 12:27:10 +00:00
83c527dd91
Replace nearly-identical blocks of code that defined individual custom targets/custom commands to copy files from source to build dir with the copy_files_to_build_dir function. This reduces the number of build targets and speeds up/cleans up the make output. Signed-off-by: Mark Stemm <mark.stemm@gmail.com>
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 thedocker/localimage 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.