Closed 4d4ch4u32 closed 2 days ago
This error is not present in version 2.6.0
of the docker image.
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
@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...
Moving this to the correct repo. This needs debugging @4d4ch4u32, please help.
Which information do you need?
Redundant of https://github.com/opensearch-project/opensearch-build/issues/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 pull opensearchproject/opensearch:latest
and a t2.small
instance running in us-west-2
and it works okay:
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 x86-64-v2
🤷♂️ 😿
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: