Skip to content
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

Building Quarkus with Buildpacks uses Liberica as JDK #37777

Closed
fniephaus opened this issue Dec 15, 2023 · 3 comments · Fixed by #41936
Closed

Building Quarkus with Buildpacks uses Liberica as JDK #37777

fniephaus opened this issue Dec 15, 2023 · 3 comments · Fixed by #41936
Labels
area/native-image kind/bug Something isn't working
Milestone

Comments

@fniephaus
Copy link

Describe the bug

When following the docs on building Quarkus with Buildpacks, I end up with a container that uses Liberica as the JDK.

Expected behavior

Mandrel is used a the JDK, or the user is given a choice which JDK to use.

Actual behavior

Liberica is used as the JDK.

How to Reproduce?

$ git clone --depth 1 https://github.com/quarkusio/quarkus-quickstarts.git
$ cd quarkus-quickstarts/getting-started
$ ./mvnw quarkus:add-extension -Dextensions='container-image-buildpack'
$ ./mvnw install -Dquarkus.container-image.build=true
# ...
===> EXPORTING
Reusing layer 'paketo-buildpacks/ca-certificates:helper'
Reusing layer 'paketo-buildpacks/bellsoft-liberica:helper'
Reusing layer 'paketo-buildpacks/bellsoft-liberica:java-security-properties'
Reusing layer 'paketo-buildpacks/bellsoft-liberica:jre'
Adding 1/1 app layer(s)
Reusing layer 'buildpacksio/lifecycle:launcher'
Reusing layer 'buildpacksio/lifecycle:config'
Adding label 'io.buildpacks.lifecycle.metadata'
Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
no default process type
Saving ubuntu/getting-started:1.0.0-SNAPSHOT...
*** Images (336e9b9fad07):
      ubuntu/getting-started:1.0.0-SNAPSHOT
Adding cache layer 'paketo-buildpacks/bellsoft-liberica:jdk'
Adding cache layer 'paketo-buildpacks/syft:syft'
Adding cache layer 'paketo-buildpacks/maven:application'
Adding cache layer 'paketo-buildpacks/maven:cache'
[INFO] Buildpack build complete, with exit code 0
# ...

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

@fniephaus fniephaus added the kind/bug Something isn't working label Dec 15, 2023
Copy link

quarkus-bot bot commented Dec 15, 2023

/cc @Karm (mandrel), @galderz (mandrel), @zakkak (mandrel)

@zakkak
Copy link
Contributor

zakkak commented Dec 16, 2023

Thanks for reporting this @fniephaus.

@zakkak
Copy link
Contributor

zakkak commented Jan 11, 2024

@iocanel if I understand correctly we are not setting a builder image by default and thus buildpack uses paketo-buildpacks/bellsoft-liberica.

Since in general we don't test Quarkus with Liberica NIK and there is no buildpack using Mandrel, the next best choice for Quarkus seems to be GraalVM CE, i.e. paketo-buildpacks/graalvm/. WDYT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/native-image kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants