[PoC] in-tree compose extension with a compose stack point - #4
Draft
ndeloof wants to merge 1 commit into
Draft
Conversation
ndeloof
force-pushed
the
compose-stack-extension
branch
from
August 12, 2026 14:57
f0f65d3 to
d6b8330
Compare
Demo built on top of the extensions framework (moby#53021): - com.docker.compose.stack.v0 point: receives the resolved Compose project definition (equivalent of the resolved compose.yaml) pushed by the Compose client before up starts. Contract + mobyextgen output. - composeext builtin extension: no-op provider that only logs the received stack, exposed as a gRPC service on the daemon socket via the service.grpc point. - contrib/dind-compose-extension: docker-in-docker demo image running this dockerd, to exercise the matching Compose-side PoC. Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
ndeloof
force-pushed
the
compose-stack-extension
branch
from
August 12, 2026 15:05
d6b8330 to
b29aa8c
Compare
ndeloof
marked this pull request as draft
August 12, 2026 15:08
This was referenced Aug 12, 2026
Owner
Author
|
v2 of this PoC, ported onto the extensions framework v2 (moby#53365 — framework extracted to the external |
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.
PoC on top of the extensions framework (moby#53021), demonstrating the model discussed around docker/compose#13958: instead of a bespoke REST endpoint gated by context metadata, the "compose coordinator" pre-up push is an extension point.
extpoints/compose/stack/v0: the compose stack point —Publishreceives the resolved Compose project definition (equivalent of the resolved compose.yaml) beforeupstarts. Contract +mobyextgenoutput committed.daemon/internal/composeext: builtin no-op extension — logs the received stack, exposed as a gRPC service on the daemon socket through theservice.grpcpoint.contrib/dind-compose-extension/Dockerfile: docker-in-docker demo image running this dockerd.Validated end to end with the Compose counterpart (docker/compose#14040):
docker compose upinside the DinD producesand against a stock engine the Compose side degrades silently (Unimplemented / no h2c → debug log).
Pure demonstrator: no tests, no cleanliness intended.