-
Notifications
You must be signed in to change notification settings - Fork 2.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
Regression issue: Fast Jar not working using OpenShift and Docker strategy #16113
Comments
Seems rather serious. @iocanel can you prioritize this please? |
@geoand: roger roger |
Thanks 👍 |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Apr 1, 2021
geoand
added a commit
that referenced
this issue
Apr 1, 2021
Fix issue with fast-jar not working using OpenShift and Docker strategy
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Apr 3, 2021
Fixes quarkusio#16113 (cherry picked from commit df695f3)
mjurc
added a commit
to mjurc/quarkus-openshift-test-suite
that referenced
this issue
Apr 23, 2021
* Disabling Quarkus docker build strategy tests due to quarkusio/quarkus#16113
juazugas
pushed a commit
to juazugas/quarkus
that referenced
this issue
Sep 30, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using the Docker strategy when deploying an application using OpenShift, the build failed because the generated artifacts are not found:
Actual behavior
The build should find the artifacts in the right folder.
To Reproduce
Steps to reproduce the behavior:
mvn io.quarkus:quarkus-maven-plugin:999-SNAPSHOT:create -DprojectGroupId=org.acme -DprojectArtifactId=openshift-quickstart -DclassName="org.acme.rest.GreetingResource" -Dpath="/greeting" -Dextensions=openshift
openshift-quickstart
mvn package -Dquarkus.kubernetes.deploy=true -Dquarkus.openshift.build-strategy=docker
The maven command fails with the exception in the description.
Environment (please complete the following information):
Quarkus version or git rev
999-SNAPSHOT or 1.13.0.Final
It worked fine using 1.11+
Additional context
I think that this is a regression issue caused by the new fast jar method. If we change the target folder in the
Dockerfile.jvm
file fromtarget/quarkus-app
totarget
, then it starts working fine. (Not saying this is the right way to fix it).The text was updated successfully, but these errors were encountered: