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

Create container_engines configs in falco.yaml #3258

Closed
incertum opened this issue Jun 20, 2024 · 2 comments · Fixed by #3266
Closed

Create container_engines configs in falco.yaml #3258

incertum opened this issue Jun 20, 2024 · 2 comments · Fixed by #3266
Milestone

Comments

@incertum
Copy link
Contributor

incertum commented Jun 20, 2024

Motivation

See #3243 (comment) and additional comments after that comment.

The current favorite seems to expose new container_engines in the following format:

container_engines:
  docker:
    enabled: true
  cri:
    enabled: true
    sockets: ["/run/containerd/containerd.sock", "/run/crio/crio.sock", "/run/k3s/containerd/containerd.sock"]
    disable_async: false
  podman:
    enabled: true
  lxc:
    enabled: true
  libvirt_lxc:
    enabled: true
  bpm:
    enabled: true

This feature will allow end users to explicitly disable some container engines, plus it can help in deployment scenarios where the existing --cri and --disable-cri-async CLI flags are more difficult to configure.

@incertum
Copy link
Contributor Author

@leogr @LucaGuerra
CC @networkhell

@incertum
Copy link
Contributor Author

/milestone 0.39.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants