review Compose model-runner page to use models top level element (#22963)

<!--Delete sections as needed -->

## Description
Update Compose Model Runner page to use top level element `models`

## Related issues or tickets
N/A

## Reviews

<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->

- [ ] Technical review
- [x] Editorial review
- [ ] Product review

---------

Signed-off-by: Guillaume Lours <[email protected]>
Co-authored-by: aevesdocker <[email protected]>

Author: glours

content/manuals/ai/compose/model-runner.md

@@ -0,0 +1,116 @@
+---
+title: Use Docker Model Runner
+description: Learn how to integrate Docker Model Runner with Docker Compose to build AI-powered applications
+keywords: compose, docker compose, model runner, ai, llm, artificial intelligence, machine learning
+weight: 20
+aliases:
+ - /compose/how-tos/model-runner/
+params:
+  sidebar:
+    badge:
+      color: green
+      text: New
+---
+
+{{< summary-bar feature_name="Compose model runner" >}}
+
+Docker Model Runner can be integrated with Docker Compose to run AI models as part of your multi-container applications.  
+This lets you define and run AI-powered applications alongside your other services.
+
+## Prerequisites
+
+- Docker Compose v2.38 or later
+- Docker Desktop 4.43 or later 
+- Docker Desktop for Mac with Apple Silicon or Docker Desktop for Windows with NVIDIA GPU
+- [Docker Model Runner enabled in Docker Desktop](/manuals/ai/model-runner.md#enable-docker-model-runner)
+
+## Use `models` definition
+
+The [`models` top-level element](/manuals/ai/compose/models-and-compose.md) in the Compose file lets you define AI models to be used by your application.
+Compose can then use Docker Model Runner as the model runtime. 
+
+The following example shows how to provide the minimal configuration to use a model within your Compose application:
+
+```yaml
+services:
+  my-chat-app:
+    image: my-chat-app
+    models:
+      - smollm2
+
+models:
+  smollm2:
+    image: ai/smollm2
+```
+
+### How it works
+
+During the `docker compose up` process, Docker Model Runner automatically pulls and runs the specified model.  
+It also sends Compose the model tag name and the URL to access the model runner.
+
+This information is then passed to services which declare a dependency on the model provider.  
+In the example above, the `my-chat-app` service receives 2 environment variables prefixed by the service name:
+- `SMOLLM2_ENDPOINT` with the URL to access the model
+- `SMOLLM2_MODEL` with the model name
+
+This lets the `my-chat-app` service to interact with the model and use it for its own purposes.
+
+### Customizing environment variables
+
+You can customize the environment variable names which will be passed to your service container using the long syntax:
+
+```yaml
+services:
+  my-chat-app:
+    image: my-chat-app
+    models:
+      smollm2:
+        endpoint_var: AI_MODEL_URL
+        model_var: AI_MODEL_NAME
+
+models:
+  smollm2:
+    image: ai/smollm2
+```
+
+With this configuration, your `my-chat-app` service will receive:
+- `AI_MODEL_URL` with the URL to access the model
+- `AI_MODEL_NAME` with the model name
+
+This allows you to use more descriptive variable names that match your application's expectations.
+
+
+## Alternative configuration with Provider services
+
+> [!TIP]
+>
+> Use the []`models` top-level element](#use-models-definition) instead.
+
+Compose introduced a new service type called `provider` that allows you to declare platform capabilities required by your application. For AI models, you can use the `model` type to declare model dependencies.
+
+Here's an example of how to define a model provider:
+
+```yaml
+services:
+  chat:
+    image: my-chat-app
+    depends_on:
+      - ai_runner
+
+  ai_runner:
+    provider:
+      type: model
+      options:
+        model: ai/smollm2
+```
+
+Notice the dedicated `provider` attribute in the `ai_runner` service.   
+This attribute specifies that the service is a model provider and lets you define options such as the name of the model to be used.
+
+There is also a `depends_on` attribute in the `my-chat-app` service.  
+This attribute specifies that the `my-chat-app` service depends on the `ai_runner` service.  
+This means that the `ai_runner` service will be started before the `my-chat-app` service to allow injection of model information to the `my-chat-app` service.
+
+## Reference
+
+- [Docker Model Runner documentation](/manuals/ai/model-runner.md)

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

@@ -181,4 +181,4 @@ Cloud providers might:
 - [`models` top-level element](/reference/compose-file/models.md)
 - [`models` attribute](/reference/compose-file/services.md#models)
 - [Docker Model Runner documentation](/manuals/ai/model-runner.md)
-- [Compose Model Runner documentation](/manuals/compose/how-tos/model-runner.md)]
+- [Compose Model Runner documentation](/manuals/ai/compose/model-runner.md)

content/manuals/ai/model-runner/_index.md

@@ -84,7 +84,7 @@ Models are pulled from Docker Hub the first time they're used and stored locally
 > Using Testcontainers or Docker Compose?
 > [Testcontainers for Java](https://java.testcontainers.org/modules/docker_model_runner/)
 > and [Go](https://golang.testcontainers.org/modules/dockermodelrunner/), and
-> [Docker Compose](/manuals/compose/how-tos/model-runner.md) now support Docker Model Runner.
+> [Docker Compose](/manuals/ai/compose/model-runner.md) now support Docker Model Runner.
 
 ## Enable Docker Model Runner
 

content/manuals/compose/how-tos/model-runner.md

@@ -15,7 +15,6 @@ params:
 Docker Compose supports provider services, which allow integration with services whose lifecycles are managed by third-party components rather than by Compose itself.  
 This feature enables you to define and utilize platform-specific services without the need for manual setup or direct lifecycle management.
 
-
 ## What are provider services?
 
 Provider services are a special type of service in Compose that represents platform capabilities rather than containers.
@@ -104,6 +103,10 @@ The plugin or binary is responsible for:
 
 This information is then passed to dependent services as environment variables.
 
+> [!TIP]
+>
+> If you're working with AI models in Compose, use the [`models` top-level element](/manuals/ai/compose/models-and-compose.md) instead.
+
 ## Benefits of using provider services
 
 Using provider services in your Compose applications offers several benefits:

content/manuals/compose/how-tos/provider-services.md

@@ -219,7 +219,7 @@ For more frequently asked questions, see the [FAQs](/manuals/desktop/troubleshoo
 - Docker Model Runner is now available on x86 Windows machines with NVIDIA GPUs.
 - You can now [push models](/manuals/ai/model-runner.md#push-a-model-to-docker-hub) to Docker Hub with Docker Model Runner.
 - Added support for Docker Model Runner's model management and chat interface in Docker Desktop for Mac and Windows (on hardware supporting Docker Model Runner). Users can now view, interact with, and manage local AI models through a new dedicated interface.
-- [Docker Compose](/manuals/compose/how-tos/model-runner.md) and Testcontainers [Java](https://java.testcontainers.org/modules/docker_model_runner/) and [Go](https://golang.testcontainers.org/modules/dockermodelrunner/) now support Docker Model Runner.
+- [Docker Compose](/manuals/ai/compose/model-runner.md) and Testcontainers [Java](https://java.testcontainers.org/modules/docker_model_runner/) and [Go](https://golang.testcontainers.org/modules/dockermodelrunner/) now support Docker Model Runner.
 - Introducing Docker Desktop in the [Microsoft App Store](https://apps.microsoft.com/detail/xp8cbj40xlbwkx?hl=en-GB&gl=GB).
 
 ### Upgrades

content/manuals/desktop/release-notes.md

@@ -110,7 +110,7 @@ Compose menu:
 Compose models:
   requires: Docker Compose [2.38.0](/manuals/compose/releases/release-notes.md#2380) and later
 Compose model runner:
-  requires: Docker Compose [2.35.0](/manuals/compose/releases/release-notes.md#2350) and later, and Docker Desktop 4.41 and later
+  requires: Docker Compose [2.38.0](/manuals/compose/releases/release-notes.md#2350) and later, and Docker Desktop 4.43 and later
 Compose OCI artifact:
   requires: Docker Compose [2.34.0](/manuals/compose/releases/release-notes.md#2340) and later
 Compose provider services: