-
Notifications
You must be signed in to change notification settings - Fork 275
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
[BUG] Fatal glibc error: CPU does not support x86-64-v2 #5120
Comments
This error is not present in version |
Any update? |
Moving this to the correct repo. This needs debugging @4d4ch4u32, please help. |
@peterzhuamazon , can you please take a look and add your thoughts? |
@4d4ch4u32 , can you add details about underlying OS |
This container is used in the GitLab CI: https://git.var-lab.com/dev-tools/glubuntu-php (it's a Ubuntu with pre-installed packages, see the Dockerfile in the repository for details) But I'm not sure if the GitLab services are also running inside the "Job-Image" which is defined for the GitLab CI-job. It possible that the services are injected with another magic made by GitLab devs... |
Which information do you need? |
Redundant of #4580. This is more related to the AL2023 more than the build repo. I think @4d4ch4u32 should check the issues on https://github.com/amazonlinux/container-images or https://github.com/amazonlinux/amazon-linux-2023/. Thanks. |
I did a quick test using docker run output
|
Now that I've realised my stupidity, I'm not surprised that it works well. With an appropriate CPU. 😆 The CPU of the host I used is not supporting |
Describe the bug
Docker image v2.17.x on GitLab CI is not working, it fails with the error
Fatal glibc error: CPU does not support x86-64-v2
.Related component
Build
To Reproduce
Running OpenSearch as a service in a GitLab CI Job:
Expected behavior
OpenSearch is running in GitLab CI without errors.
Additional Details
GitLab Log:
The text was updated successfully, but these errors were encountered: