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

Fatal glibc error: CPU does not support x86 - 64 - v2 when privately deploying refly_minio #449

Open
ctwss opened this issue Feb 5, 2025 · 0 comments
Assignees

Comments

@ctwss
Copy link

ctwss commented Feb 5, 2025

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

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

No branches or pull requests

2 participants