quarkus: Warning about unsupported argument is thrown into the console when running with Mandrel

Warning about unsupported argument is thrown into the console when running native build using Mandrel image. This is usability issue, Mandrel is supposed to be the default for Quarkus and therefore no warnings should be in the console log.

Warning shown in the console:

[INFO] [io.quarkus.deployment.pkg.steps.NativeImageBuildStep] docker run .. 
Warning: Ignoring server-mode native-image argument --no-server.

Steps to reproduce:

git clone https://github.com/quarkus-qe/beefy-scenarios.git
cd beefy-scenarios/
mvn clean verify -Dnative -Dquarkus.native.container-build=true -Dquarkus.native.native-image-xmx=3g -pl 003-quarkus-many-extensions/ -Dquarkus.native.builder-image=quay.io/quarkus/ubi-quarkus-mandrel:20.1.0.1.Alpha2-java11

This is applicable to Mandrel only, GraalVM CE doesn’t throw this warning.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 19 (19 by maintainers)

Commits related to this issue

Don't use --no-server on Mandrel Fixes: #11060 — committed to geoand/quarkus by geoand 4 years ago
Merge pull request #11088 from geoand/#11060 Don't use --no-server on Mandrel — committed to quarkusio/quarkus by gsmet 4 years ago

Most upvoted comments

Yes this is intentional. The bash script allows us to tweak things without altering source code. See https://github.com/graalvm/mandrel-packaging/blob/14e3ebb4b80010cae4e01c319fc55afb70c028f4/buildJDK.sh#L98

Thank you, that helped 😃 Mandrel is new to me, I wasn’t aware of these changes.

jaikiran on Jul 30, 2020

@geoand LOL, so quick! hehe 😃

galderz on Jul 30, 2020