Discofork
Repository brief

docker/compose

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:40:17.868Z
1mo ago

docker/compose

docker/compose is the main Go-based Docker Compose implementation for defining and running multi-container applications with Docker. It is active, widely used, and heavily forked/starred, so forks are most interesting if they target Compose behavior, CLI workflow, or ecosystem integration. The repo includes product docs, build tooling, CI config, and a large internal/package layout for the Compose CLI and engine interaction.

GitHub
Loading tags...
Stars37,196
Forks5,768
Default branchmain
Last pushed2026-03-30T15:32:37Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer this fork only if you are maintaining an old Raspberry Pi/Raspbian deployment that depends on its legacy Hypriot-specific behavior. For general Compose use, upstream is a much better choice because this fork is stale, far behind, and likely missing modern fixes and platform support.

Choose this fork only if you need its custom compose monkey behavior and are willing to own a long-stale, highly divergent codebase. For normal Docker Compose usage, upstream is the safer default.

Do not adopt this as a general-purpose Compose base. It is best treated as a historical fork with heavy drift and little evidence of current support; only choose it if you specifically need the old Fig lineage or want a minimal starting point for a custom fork.

Choose this fork only if you specifically need the legacy Python Compose branch and can accept major staleness. For most adopters, upstream `docker/compose` is the better fit because it is actively maintained, platform-current, and much closer to the modern Compose ecosystem.

Prefer this fork only if its dry-run and legacy compatibility behavior are specifically what you need. For general adoption, upstream is the better choice because this fork is stale, materially behind, and likely to miss important fixes and compatibility work.

Choose this fork only if you want an upstream-like baseline with no behavioral changes; otherwise, the main `docker/compose` repo is the better choice because it is actively ahead on fixes and maintenance.

Prefer this fork only if you specifically need a pinned, near-upstream Compose v2 snapshot. If you want the latest fixes or any fork-specific enhancements, upstream is the better default.

Prefer this fork only if you specifically need legacy Compose v1 behavior. For most adopters, upstream is the better choice because it is active, much newer, and already contains the modern Compose implementation and recent fixes.

Prefer this fork only if you specifically need its legacy Python Compose behavior or its project-specific customizations. For most adopters, upstream Docker Compose is the safer choice because this fork is stale and materially diverged.

Choose this fork only if you need its bridge/transformer and modified dry-run behavior. For general Compose use, upstream is the safer choice because this fork is significantly diverged and stale.