Initialize build runner in AwtProcessor before usage

[turing85]

No description provided.

[quarkus-bot]

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

• title should not end up with dot

_{This message is automatically generated by a bot.}

[maxandersen]

can you give some context of why you need it quiet?

[turing85]

See this zulip discussion for details.

The issue was already fixed in this PR.

[gsmet]

If we have to do that, there is something wrong. I'll have to have a look later.

[turing85]

Maybe I am misusing the setup(...) method, but I can say that setup() has not yet been called when AwtProcessor is executed. Without the call to setup(...), the successive call to nativeImageRunnerBuildItem.getBuildRunner().getGraalVMVersion() would trigger the initial image pull.

[turing85]

Seems that the docker version used in github-workflows has some kind of bug:

[INFO] [io.quarkus.deployment.pkg.steps.NativeImageBuildRunner] version command: docker run --env LANG=C --rm --user 1001:123 --quiet --rm quay.io/quarkus/ubi-quarkus-mandrel-builder-image:jdk-17 --version
[INFO] [io.quarkus.deployment.pkg.steps.GraalVM] lines before filtering:
unknown flag: --quiet
See 'docker run --help'.

According to the documentation (docs.docker.com), the flag should exist. I'll remove the --quiet from run and pull again.

[turing85]

@gsmet is this Pr still relevant, or can it be closed?

[gsmet]

I think what we are doing in AwtProcessor is not really in line with what we should do. Or we should initialize things differently.

Let's merge your PR if CI passes but ideally I think we should rework this to avoid having all these quirks in the build steps.

[quarkus-bot]

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.