-
Notifications
You must be signed in to change notification settings - Fork 149
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
Optimize Dockerfile performance #55
Comments
Currently, the majority of the dockerfile build time is allocated to running the |
@schultzp2020 I think you can make the Dockerfile to use the |
@tumido I have yet to try it; however, I do not believe that will work because the last (prod) stage doesn't copy files directly from the build stage. Instead the build stage creates tarballs, which are then extracted during the prod stage. Therefore, the majority of the files are not from previous stages that would benefit from running |
I think tarball preserves permissions, doesn't it? Let's try it and if it doesn't work we can try to come up with something else... 🙂 |
End users will no longer be building their own backstage showcase images, so this issue is mainly for improving our own build times for showcase and RHDH. Currently I have only identified optimizations for the first stage (dependency installations) by only copying |
There are no optimizations we can do for the dockerfile since the |
What do you want to improve?
Optimize Dockerfile to run faster. We have many contributions and it takes a long time to get feedback, merge and deploy.
What is the current behavior?
The build time was already too long and doubled in the last week.
What is the new behavior?
Build faster. Much faster
Put an
x
in the boxes that applyThe text was updated successfully, but these errors were encountered: