Skip to content

Commit 5f68f62

Browse files
dvdksnclaudecraig-osterhout
authored
compose: clarify cloud provider portability section (#24423)
## Summary - Rewrite the "Cloud providers" section to explain that the Compose models specification enables portability for platforms that implement it, rather than implying specific named cloud providers currently support it - Remove vague "compatible cloud providers" reference from Prerequisites - Change "Cloud providers might" to "A platform might" to reflect this is a specification-level feature Closes #24257 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Craig Osterhout <craig.osterhout@docker.com>
1 parent db740fe commit 5f68f62

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

content/manuals/ai/compose/models-and-compose.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,7 @@ Compose lets you define AI models as core components of your application, so you
1616
## Prerequisites
1717

1818
- Docker Compose v2.38 or later
19-
- A platform that supports Compose models such as Docker Model Runner (DMR) or compatible cloud providers.
20-
If you are using DMR, see the [requirements](/manuals/ai/model-runner/_index.md#requirements).
19+
- A platform that supports Compose models such as [Docker Model Runner (DMR)](/manuals/ai/model-runner/_index.md#requirements).
2120

2221
## What are Compose models?
2322

@@ -166,7 +165,7 @@ Docker Model Runner will:
166165

167166
### Cloud providers
168167

169-
The same Compose file can run on cloud providers that support Compose models:
168+
The Compose models specification is portable. Platforms that implement the Compose specification can support the `models` top-level element, allowing the same Compose file to run on different infrastructure. Cloud-specific behavior can be configured using extension attributes (`x-*`):
170169

171170
```yaml
172171
services:
@@ -184,9 +183,10 @@ models:
184183
- "cloud.region=us-west-2"
185184
```
186185

187-
Cloud providers might:
186+
How a platform handles model definitions depends on its implementation. A platform might:
187+
188188
- Use managed AI services instead of running models locally
189-
- Apply cloud-specific optimizations and scaling
189+
- Apply platform-specific optimizations and scaling
190190
- Provide additional monitoring and logging capabilities
191191
- Handle model versioning and updates automatically
192192

0 commit comments

Comments
 (0)