mirror of
https://github.com/falcosecurity/falco.git
synced 2026-04-06 12:02:16 +00:00
81c53a8d29
So I might be wrong here, but I believe this is missing. I tried to build to the `docker/falco/Dockerfile` locally and push to GKE and was running into some errors getting Falco started. I checked both the GKE node, as well as the running pod and I couldn't find the script. So I think we want to include the script directly into the container. Anyway I was able to now use this Dockerfile to run my local version of Falco in GKE and load a BPF probe fine. Other thoughts: Do we want to consider pull the flags from the `falco-driver-loader` script up to the container image as an ENV or something? Other thoughts: It looks like the other container images all are based on this one so this should naturally flow down to the others. If we don't need this feel free to ignore/close. :) Signed-off-by: Kris Nova <kris@nivenly.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.