search

wazuh / wazuh-kubernetes

Wazuh - Wazuh Kubernetes
https://wazuh.com/
GNU General Public License v2.0
256 stars 160 forks source link

Fatal glibc error: CPU does not support x86-64-v2 using 4.8.0 image #719

Closed crlsgms closed 3 months ago

crlsgms commented 3 months ago

Hello everyone

I'm using rancher / kubernetes to deploy wazuh environment, using image 4.7.5 works fine but moving the same environment to use image 4.8.0 none of the pods get up (manager, indexer and dashboard image) with this cpu flags errors:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0. 2024-06-18T12:13:26.702738396Z [s6-init] ensuring user provided files have correct perms...exited 0. 2024-06-18T12:13:26.704616095Z [fix-attrs.d] applying ownership & permissions fixes... 2024-06-18T12:13:26.705900334Z [fix-attrs.d] done. 2024-06-18T12:13:26.707070342Z [cont-init.d] executing container initialization scripts... 2024-06-18T12:13:26.708733478Z [cont-init.d] 0-wazuh-init: executing... 2024-06-18T12:13:26.711356932Z Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:26.711917345Z [cont-init.d] 0-wazuh-init: exited 127. 2024-06-18T12:13:26.713240984Z [cont-init.d] 1-config-filebeat: executing... Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:26.715788109Z [cont-init.d] 1-config-filebeat: exited 127. 2024-06-18T12:13:26.718268824Z [cont-init.d] 2-manager: executing... 2024-06-18T12:13:26.720245131Z Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:26.720815351Z [cont-init.d] 2-manager: exited 127. 2024-06-18T12:13:26.722130414Z [cont-init.d] done. 2024-06-18T12:13:26.722858287Z [services.d] starting services 2024-06-18T12:13:26.729024192Z Fatal glibc error: CPU does not support x86-64-v2 Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:26.729649671Z Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:26.731340234Z [services.d] done. 2024-06-18T12:13:27.730614709Z Fatal glibc error: CPU does not support x86-64-v2 Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:27.731216046Z Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:28.731963524Z Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:28.731989815Z Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:28.732583137Z Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:29.732846500Z Fatal glibc error: CPU does not support x86-64-v2 Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:29.733367486Z Fatal glibc error: CPU does not support x86-64-v2 2024-06-18T12:13:30.734601360Z Fatal glibc error: CPU does not support x86-64-v2

I had a similar issue with mysql images earlier this year, one hack was to change the cpu delivered to kubernetes vm to host or any whitout TSX (I'm using proxmox as the hypervisor layer) mysql issue for reference

Is it possible to recompile the 4.8.0 to work without the dependency for this cpu flag? Or any workarround to pass this error to work as earlier versions?

vikman90 commented 3 months ago

Dear @crlsgms,

We have followed this case and related threads on Slack in issue https://github.com/wazuh/wazuh-packages/issues/3007. We have confirmed that this problem is related to Proxmox versions prior to 8.0, and we have the workaround you suggested resolving it, in addition to the option of upgrading Proxmox to version 8.0 or higher.

Thank you for your contribution, and best regards.