-
Notifications
You must be signed in to change notification settings - Fork 231
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
Slower than BuildKit with complex Dockerfile #116
Comments
Oh this is awesome |
Retested and still slow.. AkihiroSuda/buildbench#3 |
img is really slow to be used in local and CI systems. I really love the rootless builds. Showing some perf details:
Dockerfile
From the stats img is over 6 times slower. ping @AkihiroSuda . Any pointers , coz buildkit is faster as per your comments above. |
@frezbo I guess you're using |
@jessfraz @AkihiroSuda I really want to push engineers to use a tool that can build without root. Having docker and a user having permission to build/deploy in a CI system is basically superuser. |
Hi all, I'm facing a speed issue when I tested on Jenkins through a pipeline using an Any advice to boost a bit performance? Note that by running directly with Dockerfile mentioned (but needs specific stuff to run fully, you may omit the RUN and COPY random directory):
Thank you, Note: I asked Googlers if they could reduce the image... it seems they think about it but I don't know when they will provide a EDIT: I moved this specific CI/CD pipeline to Kaniko to build the final image... and it works fine. Within 2 minutes to build contrary to a timeout after 1h with I will keep using |
Benchmark:
Please refer to AkihiroSuda/buildbench#1 for the further information.
I think both BuildKit and img are configured to use overlayfs but maybe needs some investigation.
The text was updated successfully, but these errors were encountered: