-
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
Re-augmentation in jib image #41797
Comments
/cc @geoand (jib) |
I'm actually a little confused. Looking at:
I assume you are attempting to create a container image. But then you launch the application via:
|
I'm actually attempting to start the app with But I would expect not to have to set the |
And then the additional ask would be to have a mechanism to have the container re-augment prior to start. either with a configuration to the jib extension or with passing a environment variable to the container on start |
Ah, so these are the commands executed inside the container, correct? |
@geoand yes that's correct. |
Gotcha, I'll have a look soon |
@kpagratis can you check #41888 please? |
Sure I'll try today. Thanks! |
I just tried with the pr branch and am still seeing the exception when running |
Any chance you can attach a sample that exhibits the problem? |
Fix issue with Jib and mutable jar rebuild
Fixes: quarkusio#41797 (cherry picked from commit 18ab787)
Describe the bug
Running a re-augment in a jib image fails because it's trying to find the jar in a default location.
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
I created the image like so
when i attempt to run
java -jar -Dquarkus.launch.rebuild=true quarkus-run.jar
in the image i get the following stacktraces:I was able to get re-augmentation to work but i had to set the
quarkus.package.output-directory
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: