-
Notifications
You must be signed in to change notification settings - Fork 940
Closed
Labels
Milestone
Description
Describe the bug
After the POD restarted 8 times it worked.
ERROR: Error: Initialization issues during scap_init
Just Install it, details are below.
Expected behaviour
it should not need to restart to able to work
Environment
- Falco version:
Falco version: 0.38.2 (x86_64) - System info:
Linux version 5.10.223-212.873.amzn2.x86_64 (mockbuild@ip-10-0-60-177) (gcc10-gcc (GCC) 10.5.0 20230707 (Red Hat 10.5.0-1), GNU ld version 2.35.2-9.amzn2.0.1) Digwatch compiler #1 SMP Wed Aug 7 16:53:32 UTC 2024 - Cloud provider or hardware configuration:
- OS:
AWS Linux 2 - Kernel:
5.10 - Installation method:
EKS 1.29
helm upgrade --install falco falcosecurity/falco \
-f values.yml \
--create-namespace \
--namespace falco
values.yaml
->
tty: true
driver:
enabled: true
kind: modern_ebpf
falco:
rules_files:
- /etc/falco/falco_rules.yaml
- /etc/falco/falco-incubating_rules.yaml
- /etc/falco/falco-sandbox_rules.yaml
- /etc/falco/rules.d
rules:
- disable:
tag: T1552.005
- disable:
tag: T1565
json_output: true
extra:
env:
- name: FALCO_HOSTNAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
falcoctl:
artifact:
install:
enabled: true
follow:
enabled: true
config:
artifact:
allowedTypes:
- rulesfile
install:
resolveDeps: false
refs: [falco-rules:latest, falco-incubating-rules:latest, falco-sandbox-rules:latest]
follow:
refs: [falco-rules:latest, falco-incubating-rules:latest, falco-sandbox-rules:latest]
falcosidekick:
enabled: false
Additional context
I saw many other folks reporting this here, but it's not clear why this happened and how to fix it if there is a fix.
kirylbelavus, nadiamoe, shane-lawrence, ElSamhaa, Randoooom and 1 more