Skip to content

docs: use 'docker compose' (v2) consistently in docker/README.md - #263

Open
ygd58 wants to merge 1 commit into
ORO-AI:mainfrom
ygd58:docs/docker-compose-v2-syntax
Open

docs: use 'docker compose' (v2) consistently in docker/README.md#263
ygd58 wants to merge 1 commit into
ORO-AI:mainfrom
ygd58:docs/docker-compose-v2-syntax

Conversation

@ygd58

@ygd58 ygd58 commented Aug 28, 2026

Copy link
Copy Markdown

What

docker/README.md used the legacy hyphenated docker-compose (v1 standalone binary) in all 10 of its command examples, while README.md, docs/miner-guide.md, and docs/validator-guide.md all consistently use the modern docker compose (v2 plugin) syntax.

Why

Docker Compose v1 has been end-of-life since July 2023 and is not installed by default on current Docker Desktop / Docker Engine setups. A new contributor following docker/README.md step by step can hit docker-compose: command not found even though docker compose works fine. This just aligns the command syntax with the rest of the repo's docs — no behavior or content change otherwise.

Change

s/docker-compose/docker compose/g across docker/README.md (10 occurrences).

docker/README.md used the legacy hyphenated 'docker-compose' (v1
standalone binary) throughout, while README.md, docs/miner-guide.md,
and docs/validator-guide.md all use the modern 'docker compose'
(v2 plugin) syntax. Compose v1 has been EOL since July 2023 and
isn't installed by default on current Docker Desktop/Engine setups,
so following docker/README.md as written can fail with 'command
not found' on a fresh install. No behavior change, just aligning
the command syntax with the rest of the repo's docs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant