Conversation
hannahilea
changed the title
| # *** Note that since this is going to be used in production, the --enable-developer | ||
| # configure option should not be used. This is the only change that I think we need | ||
| # to make to the build process for production images. jhrg 3/29/26 |
There was a problem hiding this comment.
As of the current master branch, it looks like the additional build time for the docker images is on the order of 3-5 minutes longer than check, and are roughly on par with distcheck.
Note that---as compared to the previous RPM builds---our docker builds DO include running all unit tests.
Elsewhere (slack!) you noted that this was primarily for build speed reasons; if that is the primary reason, let's file it as an improvement but not block a production deployment on it?
There was a problem hiding this comment.
The --enable-developer option does not influence build speed much, if at all. The --enable-developer option to configure changes how the code is compiled. It makes the code run more slowly (by adding in a number of debugging helpers like all those BESDEBUG() lines plus a bunch more things and disabling compiler optimizations).
| # We have some contributed scripts that work with systemctl, is it worth trying to set up | ||
| # systemctl in this image? jhrg 3/29/26 |
Co-authored-by: Hannah Robertson <hannahilea@users.noreply.github.com>
Co-authored-by: Hannah Robertson <hannahilea@users.noreply.github.com>
Co-authored-by: Hannah Robertson <hannahilea@users.noreply.github.com>
|
|
|
2 participants
Description
Reference ticket: HYRAX-1973
I have some questions about the Dockerfile code
Tasks