-
Notifications
You must be signed in to change notification settings - Fork 279
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]: OpenSearch docker image is based on EOSL amazon image #4573
[Bug]: OpenSearch docker image is based on EOSL amazon image #4573
Comments
The upcoming 2.13 version is having the latest AL2023 (2023.4.20240319): The release 2.12 version is having a slightly older (1 month) image at the time of releasing (2023.3.20240312):
AL2023 will be eol at 2027, current LTS version: The old AL image should be AL1, will eol at the end of 2023; and AL2, at about 2025: Hi @Kuckkuck could you please share the exact cve scanner and commands for us to reproduce this result? Even in your description it shows as Amazon Linux 2023.3.20240312, which is the latest release at the time. Thanks. |
We use https://trivy.dev/ to scan all our images and this comes back for the 2.12.0 image:
Canonical digest sha256:40a130ec32fa38613761ed3b84fd8d7051f267cda2ab12667b649f58f22e9218 { Strange, that the older images of OpenSearch are high or critical, but none of them are rotten. |
Hi @Kuckkuck we also use trivy and we are not able to see the same result. Very interesting. Also, this seems like an issue with https://github.com/amazonlinux/container-images or https://github.com/amazonlinux/amazon-linux-2023/, as opensearch is just using the existing image provided from them. 1.x and older 2.x images are using AL2, while new images are using AL2023 since 2.10.0. |
As noted by yourself @peterzhuamazon in #4572 AmazonLinux is not officially supported by OpenSearch |
Updated compatibility chart to be more clear on the OSes we tested on. Thanks. |
Describe the bug
OpenSearch 2.12.0 docker image
The latest 2.12.0 release of OpenSearch has image layers, which are even more rotten, than older releases.
To reproduce
Use a CVE scanner for OpenSearch images.
Expected behavior
No response
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: