You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/manuals/ai/mcp-catalog-and-toolkit/catalog.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
2
title: Docker MCP Catalog
3
3
description: Learn about the benefits of the MCP Catalog, how you can use it, and how you can contribute
4
-
keywords: docker hub, mcp, mcp servers, ai agents, calatog, docker
4
+
keywords: docker hub, mcp, mcp servers, ai agents, catalog, docker
5
5
---
6
6
7
-
The [Docker MCP Catalog](https://hub.docker.com/catalogs/mcp) is a centralized, trusted registry for discovering, sharing, and running MCP-compatible tools. Seamlessly integrated into Docker Hub, it offers verified, versioned, and curated MCP servers packaged as Docker images. The catalog is also available in Docker Desktop.
7
+
The [Docker MCP Catalog](https://hub.docker.com/mcp) is a centralized, trusted registry for discovering, sharing, and running MCP-compatible tools. Seamlessly integrated into Docker Hub, it offers verified, versioned, and curated MCP servers packaged as Docker images. The catalog is also available in Docker Desktop.
8
8
9
9
The catalog solves common MCP server challenges:
10
10
@@ -32,10 +32,11 @@ Each tool in the MCP Catalog is packaged as a Docker image with metadata:
32
32
- Connect tools to their preferred agents with simple configuration through the [MCP Toolkit](toolkit.md).
33
33
- Pull and run tools using Docker Desktop or the CLI.
34
34
35
-
Each catalog entry provides:
35
+
Each catalog entry displays:
36
36
37
37
- Tool description and metadata
38
38
- Version history
39
+
- List of tools provided by the MCP server
39
40
- Example configuration for agent integration
40
41
41
42
## Use an MCP server from the catalog
@@ -44,11 +45,11 @@ To use an MCP server from the catalog, see [MCP toolkit](toolkit.md).
44
45
45
46
## Contribute an MCP server to the catalog
46
47
47
-
The MCP server registry is available at https://github.com/docker/mcp-registry. To submit an MCP server:
48
+
The MCP server registry is available at https://github.com/docker/mcp-registry. To submit an MCP server,
48
49
follow the [contributing guidelines](https://github.com/docker/mcp-registry/blob/main/CONTRIBUTING.md).
49
50
50
51
When your pull request is reviewed and approved, your MCP server is available in 24 hours on:
Copy file name to clipboardExpand all lines: content/manuals/ai/model-runner/_index.md
+35Lines changed: 35 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,41 @@ with AI models locally.
40
40
- Run and interact with AI models directly from the command line or from the Docker Desktop GUI
41
41
- Manage local models and display logs
42
42
43
+
## Requirements
44
+
45
+
Docker Model Runner is supported on the following platforms:
46
+
47
+
{{< tabs >}}
48
+
{{< tab name="Windows">}}
49
+
50
+
Windows(amd64):
51
+
- NVIDIA GPUs
52
+
- NVIDIA drivers 576.57+
53
+
54
+
Windows(arm64):
55
+
- OpenCL for Adreno
56
+
- Qualcomm Adreno GPU (6xx series and later)
57
+
58
+
> [!NOTE]
59
+
> Some llama.cpp features might not be fully supported on the 6xx series.
60
+
61
+
{{< /tab >}}
62
+
{{< tab name="MacOS">}}
63
+
64
+
- Apple Silicon
65
+
66
+
{{< /tab >}}
67
+
{{< tab name="Linux">}}
68
+
69
+
Docker Engine only:
70
+
71
+
- Linux CPU & Linux NVIDIA
72
+
- NVIDIA drivers 575.57.08+
73
+
74
+
{{< /tab >}}
75
+
{{</tabs >}}
76
+
77
+
43
78
## How it works
44
79
45
80
Models are pulled from Docker Hub the first time they're used and stored locally. They're loaded into memory only at runtime when a request is made, and unloaded when not in use to optimize resources. Since models can be large, the initial pull may take some time — but after that, they're cached locally for faster access. You can interact with the model using [OpenAI-compatible APIs](#what-api-endpoints-are-available).
SBOM build attestations describe the contents of your image,
6
-
and the packages used to build it.
5
+
SBOM attestations describe what software artifacts an image contains and the artifacts used to create the image.
7
6
aliases:
8
7
- /build/attestations/sbom/
9
8
---
10
9
11
-
Software Bill of Materials (SBOM) attestations describe what software artifacts
12
-
an image contains, and artifacts used to create the image. Metadata included in
13
-
an SBOM for describing software artifacts may include:
10
+
SBOM attestations help ensure [software supply chain transparency](/guides/docker-scout/s3c.md) by verifying the software artifacts an image contains and the artifacts used to create the image. Metadata included in an [SBOM](/guides/docker-scout/sbom.md) for describing software artifacts may include:
14
11
15
12
- Name of the artifact
16
13
- Version
17
14
- License type
18
15
- Authors
19
16
- Unique package identifier
20
17
21
-
There are benefits to indexing contents of an image during the build, as opposed
22
-
to scanning a final image. When scanning happens as part of the build, you're
23
-
able to detect software you use to build the image, that may not show up in the
24
-
final image.
18
+
Indexing the contents of an image during the build has benefits over scanning a final image. When scanning happens as part of the build, you can detect software you used to build the image, which may not show up in the final image.
25
19
26
-
The SBOMs generated by BuildKit follow the SPDX standard. SBOMs attach to the
27
-
final image as a JSON-encoded SPDX document, using the format defined by the
Docker supports SBOM generation and attestation through an SLSA-compliant build process using BuildKit and attestations. The SBOMs generated by [BuildKit](/manuals/build/buildkit/_index.md) follow the SPDX standard and attach to the final image as a JSON-encoded SPDX document, using the format defined by the [in-toto SPDX predicate](https://github.com/in-toto/attestation/blob/main/spec/predicates/spdx.md). On this page, you’ll learn how to create, manage, and verify SBOM attestations using Docker tooling.
Copy file name to clipboardExpand all lines: content/manuals/compose/how-tos/profiles.md
+14-60Lines changed: 14 additions & 60 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,6 +85,12 @@ If you want to enable all profiles at the same time, you can run `docker compose
85
85
86
86
## Auto-starting profiles and dependency resolution
87
87
88
+
When you explicitly target a service on the command line that has one or more profiles assigned, you do not need to enable the profile manually as Compose runs that service regardless of whether its profile is activated. This is useful for running one-off services or debugging tools.
89
+
90
+
Only the targeted service (and any of its declared dependencies via `depends_on`) is started. Other services that share the same profile will not be started unless:
91
+
- They are also explicitly targeted, or
92
+
- The profile is explicitly enabled using `--profile` or `COMPOSE_PROFILES`.
93
+
88
94
When a service with assigned `profiles` is explicitly targeted on the command
89
95
line its profiles are started automatically so you don't need to start them
90
96
manually. This can be used for one-off services and debugging tools.
@@ -108,72 +114,19 @@ services:
108
114
```
109
115
110
116
```sh
111
-
# Only start backend and db
117
+
# Only start backend and db (no profiles involved)
112
118
$ docker compose up -d
113
119
114
-
# This runs db-migrations (and, if necessary, start db)
115
-
# by implicitly enabling the profiles "tools"
120
+
# Run the db-migrations service without manually enabling the 'tools' profile
116
121
$ docker compose run db-migrations
117
122
```
118
123
119
-
But keep in mind that `docker compose` only automatically starts the
120
-
profiles of the services on the command line and not of any dependencies.
121
-
122
-
This means that any other services the targeted service `depends_on` should either:
123
-
- Share a common profile
124
-
- Always be started, by omitting `profiles` or having a matching profile started explicitly
125
-
126
-
```yaml
127
-
services:
128
-
web:
129
-
image: web
130
-
131
-
mock-backend:
132
-
image: backend
133
-
profiles: ["dev"]
134
-
depends_on:
135
-
- db
136
-
137
-
db:
138
-
image: mysql
139
-
profiles: ["dev"]
140
-
141
-
phpmyadmin:
142
-
image: phpmyadmin
143
-
profiles: ["debug"]
144
-
depends_on:
145
-
- db
146
-
```
147
-
148
-
```sh
149
-
# Only start "web"
150
-
$ docker compose up -d
151
-
152
-
# Start mock-backend (and, if necessary, db)
153
-
# by implicitly enabling profiles "dev"
154
-
$ docker compose up -d mock-backend
155
-
156
-
# This fails because profiles "dev" is not enabled
157
-
$ docker compose up phpmyadmin
158
-
```
159
-
160
-
Although targeting `phpmyadmin` automatically starts the profiles `debug`, it doesn't automatically start the profiles required by `db` which is `dev`.
124
+
In this example, `db-migrations` runs even though it is assigned to the tools profile, because it was explicitly targeted. The `db` service is also started automatically because it is listed in `depends_on`.
161
125
162
-
To fix this you either have to add the `debug` profile to the `db` service:
163
-
164
-
```yaml
165
-
db:
166
-
image: mysql
167
-
profiles: ["debug", "dev"]
168
-
```
169
-
170
-
or start the `dev` profile explicitly:
171
-
172
-
```console
173
-
# Profiles "debug" is started automatically by targeting phpmyadmin
174
-
$ docker compose --profile dev up phpmyadmin
175
-
$ COMPOSE_PROFILES=dev docker compose up phpmyadmin
176
-
```
126
+
If the targeted service has dependencies that are also gated behind a profile, you must ensure those dependencies are either:
127
+
- In the same profile
128
+
- Started separately
129
+
- Not assigned to any profile so are always enabled
177
130
178
131
## Stop application and services with specific profiles
179
132
@@ -208,6 +161,7 @@ services:
208
161
```
209
162
210
163
if you only want to stop the `phpmyadmin` service, you can run
Copy file name to clipboardExpand all lines: content/manuals/compose/how-tos/project-name.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
1
---
2
2
title: Specify a project name
3
3
weight: 10
4
-
description: Understand the different ways you can set a project name in Compose and what the precedence is.
4
+
description: Learn how to set a custom project name in Compose and understand the precedence of each method.
5
5
keywords: name, compose, project, -p flag, name top-level element
6
6
aliases:
7
7
- /compose/project-name/
8
8
---
9
9
10
-
In Compose, the default project name is derived from the base name of the project directory. However, you have the flexibility to set a custom project name.
10
+
By default, Compose assigns the project name based on the name of the directory that contains the Compose file. You can override this with several methods.
11
11
12
12
This page offers examples of scenarios where custom project names can be helpful, outlines the various methods to set a project name, and provides the order of precedence for each approach.
13
13
14
14
> [!NOTE]
15
15
>
16
16
> The default project directory is the base directory of the Compose file. A custom value can also be set
17
-
> for it using the [`--project-directory` command line option](/reference/cli/docker/compose.md#use--p-to-specify-a-project-name).
17
+
> for it using the [`--project-directory` command line option](/reference/cli/docker/compose.md#options).
Copy file name to clipboardExpand all lines: content/manuals/compose/how-tos/startup-order.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
description: How to control service startup and shutdown order in Docker Compose
3
-
keywords: documentation, docs, docker, compose, startup, shutdown, order
2
+
description: Learn how to manage service startup and shutdown order in Docker Compose using depends_on and healthchecks.
3
+
keywords: docker compose startup order, compose shutdown order, depends_on, service healthcheck, control service dependencies
4
4
title: Control startup and shutdown order in Compose
5
5
linkTitle: Control startup order
6
6
weight: 30
@@ -13,7 +13,7 @@ You can control the order of service startup and shutdown with the
13
13
containers in dependency order, where dependencies are determined by
14
14
`depends_on`, `links`, `volumes_from`, and `network_mode: "service:..."`.
15
15
16
-
A good example of when you might use this is an application which needs to access a database. If both services are started with `docker compose up`, there is a chance this will fail since the application service might start before the database service and won't find a database able to handle its SQL statements.
16
+
For example, if your application needs to access a database and both services are started with `docker compose up`, there is a chance this will fail since the application service might start before the database service and won't find a database able to handle its SQL statements.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments