Skip to content

fix(init): init container compatibility on x86-64-v3 not supported cpu arch#2623

Merged
rksharma95 merged 4 commits into
kubearmor:mainfrom
rksharma95:fix-init-x86-64-v3-incompatibility
May 26, 2026
Merged

fix(init): init container compatibility on x86-64-v3 not supported cpu arch#2623
rksharma95 merged 4 commits into
kubearmor:mainfrom
rksharma95:fix-init-x86-64-v3-incompatibility

Conversation

@rksharma95

Copy link
Copy Markdown
Collaborator

Purpose of PR?:

init container was failing on amd64 cpu arch that does not support x86-64-v3

ubuntu@ubuntu:~$ kubectl get pods -n kubearmor
NAME                                        READY   STATUS                  RESTARTS       AGE
kubearmor-apparmor-containerd-2c350-hspbs   0/1     Init:CrashLoopBackOff   6 (104s ago)   9m48s
kubearmor-controller-bf9897bd6-7cpqg        1/1     Running                 2 (135m ago)   148m
kubearmor-operator-558fd84d5c-8mz4b         1/1     Running                 2 (135m ago)   150m
kubearmor-relay-6478f5ff48-w7w6s            1/1     Running                 2 (135m ago)   149m

ubuntu@ubuntu:~$ kubectl logs -n kubearmor -c init -f kubearmor-apparmor-containerd-2c350-hspbs
Fatal glibc error: CPU does not support x86-64-v3

ubuntu@ubuntu:~$ kubectl get pods -n kubearmor -o yaml | grep 'image:'
      image: docker.io/kubearmor/kubearmor:latest
    - image: docker.io/kubearmor/kubearmor-init:latest
    - image: docker.io/kubearmor/kubearmor:latest
      image: docker.io/kubearmor/kubearmor-init:latest
      image: docker.io/kubearmor/kubearmor-controller:latest
      image: docker.io/kubearmor/kubearmor-controller:latest
      image: docker.io/kubearmor/kubearmor-operator:v1.7.1
      image: docker.io/kubearmor/kubearmor-operator:v1.7.1
      image: docker.io/kubearmor/kubearmor-relay-server:latest
      image: docker.io/kubearmor/kubearmor-relay-server:latest

ubuntu@ubuntu:~$ grep -m1 flags /proc/cpuinfo
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx hypervisor lahf_lm cpuid_fault pti xsaveopt arat

ubuntu@ubuntu:~$ grep -m1 flags /proc/cpuinfo | grep -E 'avx2|fma3|bmi1|bmi2'

Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered::

Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs

ubuntu@ubuntu:~$ kubectl get pods -n kubearmor -w
NAME                                        READY   STATUS    RESTARTS       AGE
kubearmor-apparmor-containerd-2c350-qnmbl   1/1     Running   0              58s
kubearmor-controller-bf9897bd6-7cpqg        1/1     Running   2 (137m ago)   150m
kubearmor-operator-558fd84d5c-8mz4b         1/1     Running   2 (137m ago)   151m
kubearmor-relay-6478f5ff48-w7w6s            1/1     Running   2 (137m ago)   151m
^Cubuntu@ubuntu:~$ kubectl get pods -n kubearmor -o yaml | grep 'image:'
      image: docker.io/kubearmor/kubearmor:latest
    - image: docker.io/rksharma95/kubearmor-init:latest
      image: docker.io/kubearmor/kubearmor:latest
      image: docker.io/rksharma95/kubearmor-init:latest
      image: docker.io/kubearmor/kubearmor-controller:latest
      image: docker.io/kubearmor/kubearmor-controller:latest
      image: docker.io/kubearmor/kubearmor-operator:v1.7.1
      image: docker.io/kubearmor/kubearmor-operator:v1.7.1
      image: docker.io/kubearmor/kubearmor-relay-server:latest
      image: docker.io/kubearmor/kubearmor-relay-server:latest
ubuntu@ubuntu:~$ kubectl logs -n kubearmor kubearmor-apparmor-containerd-2c350-qnmbl -c init
Non-RHEL9 kernel, skipping RHEL9-specific logic
Non-RHEL9 kernel, skipping RHEL9-specific logic
\033[0;32mKernel BTF information found\033[0m
Generating vmlinux.h for kernel 6.8.0
Compiling eBPF bytecode: \033[0;32msystem_monitor.bpf.o\033[0m ...
trivy image --image-src remote docker.io/rksharma95/kubearmor-init:latest
2026-05-22T15:27:22+05:30	INFO	[vuln] Vulnerability scanning is enabled
2026-05-22T15:27:22+05:30	INFO	[secret] Secret scanning is enabled
2026-05-22T15:27:22+05:30	INFO	[secret] If your scanning is slow, please try '--scanners vuln' to disable secret scanning
2026-05-22T15:27:22+05:30	INFO	[secret] Please see also https://trivy.dev/v0.62/docs/scanner/secret#recommendation for faster secret detection
2026-05-22T15:27:28+05:30	INFO	Detected OS	family="alpine" version="3.22.4"
2026-05-22T15:27:28+05:30	WARN	This OS version is not on the EOL list	family="alpine" version="3.22"
2026-05-22T15:27:28+05:30	INFO	[alpine] Detecting vulnerabilities...	os_version="3.22" repository="3.22" pkg_num=87
2026-05-22T15:27:28+05:30	INFO	Number of language-specific files	num=0

Report Summary

┌────────────────────────────────────────────────────────────┬────────┬─────────────────┬─────────┐
│                           Target                           │  Type  │ Vulnerabilities │ Secrets │
├────────────────────────────────────────────────────────────┼────────┼─────────────────┼─────────┤
│ docker.io/rksharma95/kubearmor-init:latest (alpine 3.22.4) │ alpine │        0        │    -    │
└────────────────────────────────────────────────────────────┴────────┴─────────────────┴─────────┘
Legend:
- '-': Not scanned
- '0': Clean (no security findings detected)

Checklist:

  • Bug fix.
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • PR Title follows the convention of <type>(<scope>): <subject>
  • Commit has unit tests
  • Commit has integration tests

Aryan-sharma11
Aryan-sharma11 previously approved these changes May 25, 2026
AryanBakliwal
AryanBakliwal previously approved these changes May 26, 2026
@rksharma95 rksharma95 dismissed stale reviews from AryanBakliwal and Aryan-sharma11 via c21e20d May 26, 2026 05:27
@rksharma95 rksharma95 force-pushed the fix-init-x86-64-v3-incompatibility branch from 5b8aef5 to 88a4c63 Compare May 26, 2026 06:14
@rksharma95 rksharma95 merged commit 0b9bc0d into kubearmor:main May 26, 2026
21 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants