refly-ai / refly-ai/refly

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

Open
#449 0 comments 1 reaction 1 assignee View on GitHub

@mrcfps is already working on this.

Since Feb 5, 2025.

Dominant language
TypeScript
Stars
7.5k
Forks
729
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.