Description
We use a bake file that has hundreds of targets. These targets are all small variations of some common base images with different package versions installed. We would like to rebuild those images from time to time to get updates for the base packages.
However, we have repeatedly hit the issue that some random part of this process fails, for example because some Ubuntu packages archive for arm64 was just updated at the wrong time, some other package mirror is unavailable, etc... This then means that the whole build aborts, because one specific variant could not be build.
For us, it would be acceptable if a failure to build one image does not abort the whole build, but lets the other, unaffected builds continue as normal. We could then add some logic to retry the failed items at a later time.
Would it be possible to implement such a "--continue-on-error" option?
Description
We use a bake file that has hundreds of targets. These targets are all small variations of some common base images with different package versions installed. We would like to rebuild those images from time to time to get updates for the base packages.
However, we have repeatedly hit the issue that some random part of this process fails, for example because some Ubuntu packages archive for arm64 was just updated at the wrong time, some other package mirror is unavailable, etc... This then means that the whole build aborts, because one specific variant could not be build.
For us, it would be acceptable if a failure to build one image does not abort the whole build, but lets the other, unaffected builds continue as normal. We could then add some logic to retry the failed items at a later time.
Would it be possible to implement such a "--continue-on-error" option?