Running

Run Falco as a service

If you installed Falco by using the DEB or the RPM package, you can start the service by running:

systemctl enable falco

systemctl start falco

You can also view the Falco logs using journalctl.

journalctl -fu falco

Run Falco manually

If you'd like to run Falco by hand, you can find the full usage description for Falco by typing:

falco --help

Run within Docker

Falco ships a set of official docker images. The images can be used in two ways as follows:

• Least privileged (recommended)
• Fully privileged

Least privileged (recommended)

This is how the Falco userspace process can be ran in a container.

Once the kernel module has been installed directly on the host system, it can be used from within a container.

1. Install the kernel module:

   • You can use an official installation method directly on the host
   • Alternatively, you can temporarily use a privileged container to install the driver on the host:

   docker pull falcosecurity/falco-driver-loader:latest
   docker run --rm -i -t \
       --privileged \
       -v /root/.falco:/root/.falco \
       -v /proc:/host/proc:ro \
       -v /boot:/host/boot:ro \
       -v /lib/modules:/host/lib/modules \
       -v /usr:/host/usr:ro \
       -v /etc:/host/etc:ro \
       falcosecurity/falco-driver-loader:latest
   

The falcosecurity/falco-driver-loader image just wraps the falco-driver-loader script. You can find more about its usage here

2. Run Falco in a container using Docker with the principle of least privilege:

   docker pull falcosecurity/falco-no-driver:latest
   docker run --rm -i -t \
       -e HOST_ROOT=/ \
       --cap-add SYS_PTRACE --pid=host $(ls /dev/falco* | xargs -I {} echo --device {}) \
       -v /var/run/docker.sock:/var/run/docker.sock \
       falcosecurity/falco-no-driver:latest
   

docker info | grep -i apparmor

To run Falco in least privileged mode with the eBPF driver, we list all the required capabilities:

• on kernels <5.8, Falco requires CAP_SYS_ADMIN, CAP_SYS_RESOURCE and CAP_SYS_PTRACE
• on kernels >=5.8, CAP_BPF and CAP_PERFMON were separated out of CAP_SYS_ADMIN, so the required capabilities are CAP_BPF, CAP_PERFMON, CAP_SYS_RESOURCE, CAP_SYS_PTRACE. Unfortunately, Docker does not yet support adding the two newly introduced capabilities with the --cap-add option. For this reason, we continue using CAP_SYS_ADMIN, given that it still allows performing the same operations granted by CAP_BPF and CAP_PERFMON. In the near future, Docker will support adding these two capabilities and we will be able to replace CAP_SYS_ADMIN.

1. Install the eBPF probe

   docker pull falcosecurity/falco-driver-loader:latest
   docker run --rm -i -t \
       --privileged \
       -v /root/.falco:/root/.falco \
       -v /proc:/host/proc:ro \
       -v /boot:/host/boot:ro \
       -v /lib/modules:/host/lib/modules:ro \
       -v /usr:/host/usr:ro \
       -v /etc:/host/etc:ro \
       falcosecurity/falco-driver-loader:latest bpf
   

2. Then, run Falco

   docker pull falcosecurity/falco-no-driver:latest
   docker run --rm -i -t \
       --cap-drop all \
       --cap-add sys_admin \
       --cap-add sys_resource \
       --cap-add sys_ptrace \
       -v /var/run/docker.sock:/host/var/run/docker.sock \
       -e FALCO_BPF_PROBE="" \
       -v /root/.falco:/root/.falco \
       -v /etc:/host/etc \
       -v /proc:/host/proc:ro \
       falcosecurity/falco-no-driver:latest
   

Fully privileged

To run Falco in a container using Docker with full privileges use the following commands.

If you want to use Falco with the Kernel module driver:

docker pull falcosecurity/falco:latest
docker run --rm -i -t \
    --privileged \
    -v /var/run/docker.sock:/host/var/run/docker.sock \
    -v /dev:/host/dev \
    -v /proc:/host/proc:ro \
    -v /boot:/host/boot:ro \
    -v /lib/modules:/host/lib/modules:ro \
    -v /usr:/host/usr:ro \
    -v /etc:/host/etc:ro \
    falcosecurity/falco:latest

Alternatively, you can use the eBPF probe driver:

docker pull falcosecurity/falco:latest
docker run --rm -i -t \
    --privileged \
    -e FALCO_BPF_PROBE="" \
    -v /var/run/docker.sock:/host/var/run/docker.sock \
    -v /proc:/host/proc:ro \
    -v /boot:/host/boot:ro \
    -v /lib/modules:/host/lib/modules:ro \
    -v /usr:/host/usr:ro \
    -v /etc:/host/etc:ro \
    falcosecurity/falco:latest

It is also possible to use falco-no-driver and falco-driver-loader images in fully privileged mode. This may be desirable in environments which do not allow the full Falco image due to space, resource, security or policy constraints. You can load the eBPF probe or kernel module in its own temporary container as below:

docker pull falcosecurity/falco-driver-loader:latest
docker run --rm -i -t \
    --privileged \
    -v /var/run/docker.sock:/host/var/run/docker.sock \
    -v /dev:/host/dev \
    -v /proc:/host/proc:ro \
    -v /boot:/host/boot:ro \
    -v /lib/modules:/host/lib/modules:ro \
    -v /usr:/host/usr:ro \
    -v /etc:/host/etc:ro \
    falcosecurity/falco-driver-loader:latest

Once this has been done, or if you have installed the driver on the host permanently via the falco-driver-loader script instead of the Docker image, then you can simply load up the falco-no-driver image in privileged mode:

docker pull falcosecurity/falco-no-driver:latest
docker run --rm -i -t \
    --privileged \
    -v /var/run/docker.sock:/host/var/run/docker.sock \
    -v /dev:/host/dev \
    -v /proc:/host/proc:ro \
    falcosecurity/falco-no-driver:latest

To use falco-no-driver and falco-driver-loader with the eBPF probe you have to remove the -v /dev:/host/dev (which is only required by the Kernel Module) and add:

    -e FALCO_BPF_PROBE="" -v /root/.falco:/root/.falco \

Other configurable options:

• DRIVER_REPO - See the Installing the driver section.
• SKIP_DRIVER_LOADER - Set this environment variable to avoid running falco-driver-loader when the falcosecurity/falco image starts. Useful when the driver has been already installed on the host by other means.

Hot Reload

This will reload the Falco configuration and restart the engine without killing the pid. This is useful to propagate new config changes without killing the daemon.

kill -1 $(cat /var/run/falco.pid)