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

Falco pods failing in RHEL 8.10 #698

Open
ajinkya1986 opened this issue Jun 26, 2024 · 1 comment
Open

Falco pods failing in RHEL 8.10 #698

ajinkya1986 opened this issue Jun 26, 2024 · 1 comment
Labels
kind/bug Something isn't working lifecycle/stale

Comments

@ajinkya1986
Copy link

ajinkya1986 commented Jun 26, 2024

We have been trying to install falco helm chart on RHEL 8.10. After a few seconds the pod go into init error and then they are not visible in any of the namespaces. Following is the configuration on which we were trying to install the falco charts.

Error:

Defaulted container "falco" out of falco, falcoctl-artifact-follow, faclo-driver-loader (init), falco-artifact-install (init)
Error from server (Bad request) container "faclo" in pod "xxxx-falco-zw3rr" is waiting to start: PodInitializing

Event Details:

Type Reason Age From. Message
Warning Backoff 80s kubelet Back-off restarting failed container falco-driver-loader in pod (some_pod)

OS Details:

NAME="Red Hat Enterprise Linux"
VERSION="8.10 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.10"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.10 (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"

Kernel Version: 4.18.0-553.5.1.el8_10.x86_64

Kubernetes Version: 1.29.3

CPU: 8 cores
Memory: 16 GiB

@ajinkya1986 ajinkya1986 added the kind/bug Something isn't working label Jun 26, 2024
@poiana
Copy link
Contributor

poiana commented Sep 24, 2024

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working lifecycle/stale
Projects
None yet
Development

No branches or pull requests

2 participants