You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the private deployment of refly_minio, a Fatal glibc error: CPU does not support x86 - 64 - v2 occurred. This error indicates that the current CPU does not support the x86 - 64 - v2 instruction set required by the MinIO image.
Possible Solution
After conducting in - depth research and testing, we have found that appending the -cpuv1 suffix to the MinIO image name can effectively resolve the Fatal glibc error: CPU does not support x86 - 64 - v2 issue. This suffix is designed for systems with CPUs that do not support the x86 - 64 - v2 instruction set.
To implement this solution, you need to modify the image field within the docker - compose.yml file. Specifically, change the original image reference:
image: minio/minio:RELEASE.2025-01-20T14-49-07Z
to the updated version with the -cpuv1 suffix:
image: minio/minio:RELEASE.2025-01-20T14-49-07Z-cpuv1
The text was updated successfully, but these errors were encountered:
Description
During the private deployment of refly_minio, a Fatal glibc error: CPU does not support x86 - 64 - v2 occurred. This error indicates that the current CPU does not support the x86 - 64 - v2 instruction set required by the MinIO image.
Possible Solution
After conducting in - depth research and testing, we have found that appending the -cpuv1 suffix to the MinIO image name can effectively resolve the Fatal glibc error: CPU does not support x86 - 64 - v2 issue. This suffix is designed for systems with CPUs that do not support the x86 - 64 - v2 instruction set.
To implement this solution, you need to modify the image field within the docker - compose.yml file. Specifically, change the original image reference:
image: minio/minio:RELEASE.2025-01-20T14-49-07Z
to the updated version with the -cpuv1 suffix:
image: minio/minio:RELEASE.2025-01-20T14-49-07Z-cpuv1
The text was updated successfully, but these errors were encountered: