Summary
The user is looking for a way to use remote BuildKit to output artifacts instead of images to reduce their pipeline build time from 17 minutes to 12 minutes. They have tried different options and configurations but have been unable to save or push images locally. The user is seeking advice from others who may have faced a similar issue and expresses surprise at not encountering this problem before, suggesting it feels like a bug due to the conflicting behavior of the --artifact option.
rrjjvv
I'm surprised I haven't run into that before, and I have no clever ideas for workarounds. And yeah, that logic is wicked. That feels like a bug, especially since --artifact --image is explicitly disallowed even though that's the way --artifact behaves.
ingwar
In the code there is like milion of if's regarding the pushing/not pushing the images..
ingwar
Is there any possible way when using remote buildkit of not outputting images but outputting artefacts.
In case of one of our pipelines it changes 17minutes to 12 minutes.
I think I have checked all possible options.. even doing some strange dance with “not direct” calls, but everytime Im not saving image locally im not pushing it as well..
Anyone found any “way” of doing it?
In the code there is like milion of if's regarding the pushing/not pushing the images..