The `infra.yaml` code block under Step 6 (Structure your project with
multiple Compose files) was nested inside an ordered list, which left
stray leading whitespace on `services:` and `volumes:`. When users
copy-paste the example verbatim, `docker compose` fails with:
go-yaml load error in parser at L13.C1: did not find expected <document
start>
This change aligns the YAML with the standard 0/2/4-space indent used
elsewhere in the tutorial, and also normalizes the leading whitespace of
the surrounding code fence.
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Signed-off-by: aevesdocker <allie.sadler@docker.com>
The Compose Bridge Model Runner page said `enabled: false` means “no
Docker Model Runner resources are deployed,” which clashes with the
Desktop section that still points workloads at the host Model Runner.
Clarified that the zero-replica note is only about the in-cluster
deployment.
Fixes#25485
Signed-off-by: Dean Chen <862469039@qq.com>
The default-network paragraph pointed "use a different driver" at
network_mode (host/none/service). That's the container network stack,
not the Compose network driver.
Signed-off-by: Dean Chen <862469039@qq.com>
### Description
Adds a NOTE callout to the Compose secrets guide stating that secrets
are supported on Linux containers only, with the reason.
The page states secrets are delivered as a bind mount at
`/run/secrets/<secret_name>`, with no platform caveat. On Windows
containers this fails at container creation:
```
invalid mount config for type "bind": source path must be a directory
```
Windows containers can't bind-mount a single file, only directories — a
platform limitation confirmed by maintainers in moby/moby#37120 and
docker/cli#2055. Because Compose secrets are single-file bind mounts,
they can't work on Windows containers.
Tested on a Windows Server 2025 container
(`mcr.microsoft.com/windows/server:ltsc2025`), Hyper-V isolation, Docker
29.6.1, Compose v2.
Fixes#25540
### Related issues or tickets
- #25540
- moby/moby#37120
- docker/cli#2055
### Reviews
- [ ] Technical review
- [ ] Editorial review
## Description
Clarify that Compose v5 uses the same Docker Compose CLI command and is
functionally identical to Compose v2. Link to the existing Go SDK
documentation for the primary distinction.
## Related issues or tickets
Closes#25529
## Reviews
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
As per Craigs number-crunching, this PR removes some vvvvv old and
unused redirects 🧹
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
Replaces @material-symbols/svg-400 (5.5 MB) with heroicons (488 KB) — an
11x reduction in icon asset size. Heroicons uses a single consistent
distribution format (24px solid SVGs, fill="currentColor") eliminating
the need for the separate utils/svg.html partial, the icon-svg-stroke CSS
utility, and the dual-path resolution logic in icon.html.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
## Summary
Fix wording in the Compose extends documentation by changing `re-use` to
`reuse`.
## Related issue
N/A
## Guideline alignment
Single-file documentation wording fix with no behavior change.
## Validation
Not run locally; documentation-only change.
Co-authored-by: Codex <codex@openai.com>
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
## Description
- Update the Compose features page to use `reuse`/`Reusing` instead of
the hyphenated forms.
## Related issues or tickets
- N/A (trivial docs wording fix)
## Reviews
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
## Guideline alignment
- Reviewed `CONTRIBUTING.md` and the PR template before editing.
- Kept the diff to one documentation file with no behavior changes.
## Validation
- Not run (docs-only wording change).
---------
Co-authored-by: rohan436 <rohan.santhoshkumar@googlemail.com>
The existing warning says standalone is "not recommended" but gives
no guidance on what to use instead. Add links to Docker Desktop and
the Compose plugin as the preferred alternatives, and clarify that
standalone is only appropriate when neither option is available.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
## Summary
Updated Compose production readiness language to use present-tense
framing instead of stale time-relative language.
## Changes
- Replaced "has traditionally been focused on development and testing
workflows, but with each release we're making progress on more
production-oriented features" with present-tense language that
accurately reflects Compose's current production capabilities
- Changed from developer perspective ("we're making progress") to
user-focused language
- Removed suggestion that Compose is still becoming production-ready
Fixes#24343
---
🤖 Generated with [Docker Agent](https://github.com/docker/docker-agent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
## Summary
Fixed inconsistent version reference in Compose history documentation to
mention both v2 and v5.
## Changes
- Updated statement about Compose file format 1 compatibility to
reference both Compose v2 and v5 instead of only v2, making it
consistent with the document's scope
Fixes#24344
---
🤖 Generated with [Docker Agent](https://github.com/docker/docker-agent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
## Summary
Changed `build: alpine` to `build: ./alpine` in extends examples to
clarify it's a directory path, not an image name.
## Changes
- Updated two examples in extends documentation to use `build: ./alpine`
instead of `build: alpine` to avoid confusion with the Alpine Docker
image
Fixes#24158
---
🤖 Generated with [cagent](https://github.com/docker/cagent)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
<!--Delete sections as needed -->
## Description
Removes 'new' badges for items that are no longer new
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
Updates Compose history and development page with v5 info
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
As discussed before xmas, we will be removing opensource release note
pages and pointing users directly to the GitHub page
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
Part of the discussions with Compose team at the offsite, we agreed to
remove the migration page as we now have v5 and v1 stopped receiving
support 4 years ago. Visits to this page are minimal. Redirects are to
the main Compose landing page now and Vale error is to vvv old Desktop
release pages that are no longer visible
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
Removes the redundant sample apps page in the Compose docs, as per
discussions with the Compose team.
This page isn't really visited and it includes content that links to
other Compose docs pages. The link to the sample apps repo is better
served on other pages such as the quickstart tutorial. Redirects to the
Quickstart page
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
## Description
Note: I can't run `hugo mod vendor`:
```
$ hugo mod vendor
WARN deprecated: the ":slugorfilename" permalink token was deprecated in Hugo 0.144.0 and will be removed in a future release. Use ":slugorcontentbasename" instead.
Error: html/template:redirect/single.html:1:13: no such template "_internal/alias.html"
```
## Related issues or tickets
## Reviews
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
## Description
This PR updates control startup example to prevent Compose from
interpolating values intended as shell command arguments.
Current example yields the following warnings:
```bash
WARN[0000] The "POSTGRES_USER" variable is not set. Defaulting to a blank string.
WARN[0000] The "POSTGRES_DB" variable is not set. Defaulting to a blank string.
```
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
This pull request corrects a minor typo in the Compose Bridge
documentation to improve clarity.
- Documentation:
* Fixed a typo in the description of the Compose Bridge feature in
`content/manuals/compose/bridge/_index.md` ("geneterates" →
"generates").
