fix: do not use compose bake - #3462
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
Dzeranov
approved these changes
Jul 16, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue tracking
No
Context behind the change
Starting from v2.38.x Docker Compose delegates build process to Buildx Bake by default and because of that neither
COMPOSE_PARALLEL_LIMITnor--parallelconfiguration options not supported, so when we attempt to build all of our docker service locally by runningmake services-upit can eventually fail due to exceeding RAM on developer machine. In order to workaround it - disable usage of Buildx Bake for now. Later we have next options:build-servicethat requires services list andbuild-all-servicesthat will batch all services in groups under the hoodRef to Docker Compose issues: docker/compose#13043
How has this been tested?
make build-serviceswith latest Docker Compose; make sure build finishes and RAM not exceededRelease plan
Just merge
Potential risks; What to monitor; Rollback plan
No