Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow exe_running_docker_save in the "Write below rpm database" rule #552



None yet
2 participants
Copy link

commented Mar 7, 2019


When building a Docker container image from a Jenkins container running in Kubernetes, we get:

  "": "host",
  "evt.time": 1551362688881207853,
  "": "/var/lib/rpm/Sigmd5",
  "": null,
  "": null,
  "proc.cmdline": "exe /var/lib/docker/overlay2/67a775b844bc804f5e268e08c1e0bbc67fd4f2e4c23b3edaf2a2ef9043e49982/diff",
  "proc.pcmdline": "dockerd -H fd:// --ip-masq=false --iptables=false --log-driver=json-file --log-level=warn --log-opt=max-file=5 --log-opt=max-size=10m --storage-driver=overlay2",
  "proc.pname": "dockerd"

That alert is confusing because it says exe is writhing in /var/lib/rpm on the host. What is really happening is Docker building an image.

Adding and not exe_running_docker_save in the Write below rpm database rule fixes the alert. I've been running with that rule for over a week, it works! :)

JPLachance added some commits Mar 1, 2019

Allow exe running Docker save to write below rpm database
falco-CLA-1.0-contributing-entity: Coveo Solutions Inc.
falco-CLA-1.0-signed-off-by: Jean-Philippe Lachance <>

This comment has been minimized.

Copy link

commented Mar 14, 2019

Thanks for the contribution!

@mstemm mstemm merged commit 7689282 into falcosecurity:dev Mar 14, 2019

1 check passed

Travis CI - Pull Request Build Passed

@JPLachance JPLachance deleted the JPLachance:feature/docker-save-write-below-rpm branch Mar 14, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.