-
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: Make container-based generation opt-out #25427
Conversation
This comment has been minimized.
This comment has been minimized.
1c65aef
to
39161dd
Compare
This comment has been minimized.
This comment has been minimized.
Thanks for this. Can elaborate a little more on the reasoning? Why would one need |
My personal use case is a CI pipeline that runs in Bitbucket Pipelines. Bitbucket Pipelines gives me access to a restricted Docker daemon with some peculiarities about it. One such peculiarity is that the user ID that you pass to the container using On the other hand I can select the container that the build pipeline itself runs in, so I can easily make it use the same exact container image that I use as my target Jib base image (or one derived from it). I checked—creating the AppCDS archive in the build container itself works fine. It is only when I add Jib to the mix that it fails because the Jib target image is detected as an image to run the AppCDS build in (which is usually what you want, just not in my particular case) and so it attempts to use Docker to do the AppCDS, which fails due to the above-mentioned reasons. (You could also use it to build entirely without a container runtime, which is one of the advantages of using Jib.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@benkard mind rebasing this onto Thanks |
This change adds a new configuration key, quarkus.package.appcds-use-container, which defaults to true and can be set to false to avoid the use of a container when building an AppCDS archive. This is useful in cases where the build happens in an environment without full control of a container system, such as hosted CI solutions.
39161dd
to
b2020b7
Compare
This change adds a new configuration key,
quarkus.package.appcds-use-container
, which defaults to true and can be set to false to avoid the use of a container when building an AppCDS archive.This is useful in cases where the build happens in an environment without full control of a container system, such as hosted CI solutions.