[CELEBORN-2390] Add docker-compose for local cluster - #3768
Open
yew1eb wants to merge 3 commits into
Open
Conversation
yew1eb
force-pushed
the
add-docker-compose
branch
3 times, most recently
from
July 25, 2026 07:27
e17f836 to
0c8a74e
Compare
yew1eb
force-pushed
the
add-docker-compose
branch
from
July 25, 2026 07:33
0c8a74e to
b6fce04
Compare
Contributor
Author
|
@SteNicholas @RexXiong @zaynt4606 Could you help review this PR? Thanks! |
Contributor
Author
|
Ping @pan3793, @cxzl25, @RexXiong, @SteNicholas |
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
1 participant
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.
What changes were proposed in this pull request?
Add a
docker-compose.yamlunderdocker/to run a minimal local Celeborn cluster (1 master + 3 workers) for development and debugging, with abuild-image.shwrapper and aconf/. The existingdocker/Dockerfileis unchanged.Why are the changes needed?
There is no lightweight local deployment path today — only the K8s Helm chart or running master/worker manually on the host.
Does this PR resolve a correctness bug?
Does this PR introduce any user-facing change?
How was this patch tested?
Ran the cluster locally with
docker compose up -d: