[error]: Build step io.quarkus.deployment.pkg.steps.NativeImageBuildStep#build threw an exception: java.lang.RuntimeException: Failed to get GraalVM version #37272
Assignees
Labels
Milestone
Comments
|
/cc @Karm (mandrel), @evanchooly (kotlin), @galderz (mandrel), @geoand (kotlin), @zakkak (mandrel) |
|
Hi @tglaeser , can you please run: and paste the output? |
|
Here is full stack trace, the info logging is attached: |
|
@tglaeser can you please attach the |
@tglaeser done. Can you please run the following and share the output? This is the command Quarkus uses on your machine to determine the GraalVM/Mandrel version. |
|
@tglaeser consider visiting https://support.github.com/request?q=delete+issue+attachment and pasting the attachment url to permanently delete the attachment. It doesn't let me do it since I am not the uploader. |
|
Yeah, I tried something similar and it always succeeds without error but returned nothing. I assume this is a Windows/WSL issue. Adding the |
|
Interesting, we have not seen this before, but I see others have docker/cli#3586 and there is also a potential fix docker/cli#4548. I guess the trivial thing to do in Quarkus would be to add |
|
I think this is a frequent issue with Docker on Windows; please also see kubernetes-sigs/kind#3065 in this context. From there I gather it should be save to always use option But at a minimum, you might want to default to a (configurable) default version in case your query doesn't return any value. |
I would still prefer to apply it only when necessary, so IMO we need a way to tell whether the docker engine is running WSL or not.
We have considered this in the past and concluded it is not a good idea, as it will most probably result in Quarkus assuming a different version than the one actually being used. Furthermore, it's a clear sign that something is going wrong. Regarding making the version configurable, we have also considered this in the past (especially for testing dev versions that Quarkus doesn't recognize yet) but it turned out to be rather complicated, since different Mandrel/GraalVM versions print the version info in different formats with the more recent ones printing the info we are interested in in more than one line (see #34161). So unfortunately it is not as simple as passing something like |
|
Hi! I already reported this some time ago with WSL and Rancher Desktop (still not working! 3.5.0): #32215 |
Reading through the docker man page again I would respectfully disagree. I understand that you are executing Now I understand that in certain environments you can omit parts of the statement, but this doesn't mean that the fully qualified statement becomes invalid. As far as the determination of the host's operating system goes, using your original command while getting an empty result apparently tells you that it is Windows/WSL. Alternatively you should be able to parse the output of the |
No, the argument is being passed to the command/program as a parameter (see
There is no interaction through standard input in our case which renders the use of I understand and totally get that till this gets fixed upstream a Quarkus workaround would be desirable and I am trying to see what would be the best way to achieve this without affecting all the other use cases (which are actually working as they should).
That's not true. It only tells me that something is going wrong. I can use that to try and see if using
Not sure that would be enough either. I suspect the same issue reproduces if the docker client is running on Windows but the docker server is on WSL. |
|
I'm not sure if the referenced I'm using Rancher Desktop version The same is true for command |
zakkak
added a commit
to zakkak/quarkus
that referenced
this issue
Nov 29, 2023
There seems to be an issue with docker printing output when running in Windows' WSL without `--interactive`. Closes quarkusio#37272
zakkak
added a commit
to zakkak/quarkus
that referenced
this issue
Nov 29, 2023
There seems to be an issue with docker printing output when running in Windows' WSL without `--interactive`. Closes quarkusio#37272
zakkak
added a commit
to zakkak/quarkus
that referenced
this issue
Nov 29, 2023
There seems to be an issue with docker printing output when running in Windows' WSL without `--interactive`. Closes quarkusio#37272
zakkak
added a commit
to zakkak/quarkus
that referenced
this issue
Nov 29, 2023
There seems to be an issue with docker printing output when running in Windows' WSL without `--interactive`. Closes quarkusio#37272
gsmet
pushed a commit
to zakkak/quarkus
that referenced
this issue
Nov 30, 2023
There seems to be an issue with docker printing output when running in Windows' WSL without `--interactive`. Closes quarkusio#37272
holly-cummins
pushed a commit
to holly-cummins/quarkus
that referenced
this issue
Feb 8, 2024
There seems to be an issue with docker printing output when running in Windows' WSL without `--interactive`. Closes quarkusio#37272
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I created and downloaded the most simple Quarkus application from https://code.quarkus.io/ using
Gradle with Kotlin DSLasBuild Tool.What works:
What doesn't work:
It fails with
Output of
uname -aorverOutput of
java -versionMandrel or GraalVM version (if different from Java)
No response
Quarkus version or git rev
Build tool (ie. output of
mvnw --versionorgradlew --version)Additional information
No response
The text was updated successfully, but these errors were encountered: