ci: use build-push-action for docker build job #7176
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
louib
force-pushed
the
VL-3538
branch
2 times, most recently
from
d02fc48 to
81cf13c
Compare
andrew-scott-fischer
approved these changes
Oct 6, 2025
louib
changed the title
MohammedRyaan786
approved these changes
Oct 7, 2025
kamleshmugdiya
approved these changes
Oct 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm also setting up
buildxwhich is really what makes it possible to build the image without reaching the memory limit of the current runner. Withoutbuildx, the job would run for ~12 minutes and then silently fail, I'm assuming because it was reaching the memory limit when exporting the layersTICKET: VL-3538