-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
Use Wolfi OS as the Base Docker Image of Seata Server to reduce CVE #6964
Comments
Click to expand to view the results🐲🐲🐲🐲🐲🐲🐲🐲🐲
|
In the next version, we will use eclipse-temurin jdk. Please see here.980ba23#diff-9136d7ee194d90376becf626f92179e6d99617d858ce125f6f73ca09fa410840R53 |
Starting from version 2.3, the base image will be fully transitioned to the Eclipse Temurin JDK image |
sdk install java 23-open
sdk use java 23-open
git clone [email protected]:apache/incubator-seata.git
cd ./incubator-seata/
./mvnw -T 4C clean package -Dimage.name=eclipse-temurin:21.0.4_7-jdk -Pimage,release-image-based-on-java21 -DskipTests -e -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn; Click me to view Error Log🐲🐲🐲🐲🐲🐲🐲🐲🐲
|
An additional issue can be opened regarding the inability to support JDK 23 builds. |
|
Why you need it?
Is your feature request related to a problem? Please describe in details
org.apache.seata:seata-all:2.1.0
oracle/graalvm-reachability-metadata#542. Since I am not personally familiar with Seata Client's handling of Spring, I plan to temporarily submit Seata Client's GraalVM Reachability Metadata to https://github.com/oracle/graalvm-reachability-metadata .apache/seata-server:2.2.0
, and most of them are not related to Seata.How it could be?
A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.
openjdk:8u342
, which brings too many CVEs. I'm personally not sure if Seata Server uses anything JDK8 specific.Other related information
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: