-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
AppCDS docs on usage with JIB are slightly misleading #43733
Comments
/cc @geoand (jib) |
Can you elaborate a little more on this? Thanks |
Sure. I was reading this blog post on project Leyden, which lead me to Quarkus’ AppCDS guide. There, I was reminded about jib. I remembered reading about it before on the container image guide but I had never given it much attention because I skipped straight to docker (which was familiar). |
Thanks a lot! Your description is spot on (took me a while to remember how this works). Would you like to enhance the documention along the lines of your proposal? |
I could give it a go, sure, but now I’m wondering if it wouldn’t make more sense to change the default of the flag when it detects jib is used. Is that actually possible? |
I'll have to look at it when I have some time |
So IIUC, the machine on which you are building the container image does not have access to Docker? In that case, setting |
Indeed. So I suppose it isn't that trivial: jib can not just figure out which kind of image to build, this needs to be aligned with the Java version running the build, which could be anything. If this is working for me at this point in time, I guess I got lucky! |
What it allows us to do is pull the base image and use the Java version from it to run the AppCDS creation process locally.
That is exactly what is happening.
Jib does docker-less push, not build and that's only one of its selling points. But I do see your point. |
Thanks for clearing that out. I need to take another look at our pipeline to ensure our AppCDS setup actually works. Perhaps I'll just add docker back to the environment (it's available anyway) and still stick to jib for the simplified setup. |
Definitely! |
I’ve opened #43946 |
In the documentation on AppCDS, it is stated that "simply setting
quarkus.package.jar.appcds.enabled
totrue
" is enough when using thequarkus-container-image-jib
extension, but it is important to also setquarkus.package.jar.appcds.use-container
tofalse
(assuming that the choice for jib implies that docker is not available). Does anyone agree that it might be better to explicitly mention this?The text was updated successfully, but these errors were encountered: