Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 13 additions & 13 deletions content/manuals/accounts/create-account.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,11 +3,12 @@ title: Create a Docker account
linkTitle: Create an account
weight: 10
description: Learn how to register for a Docker ID and sign in to your account
keywords: accounts, docker ID, billing, paid plans, support, Hub, Store, Forums, knowledge
keywords:
accounts, docker ID, billing, paid plans, support, Hub, Store, Forums, knowledge
base, beta access, email, activation, verification
aliases:
- /docker-hub/accounts/
- /docker-id/
- /docker-hub/accounts/
- /docker-id/
---

You can create a free Docker account with your email address or by signing up
Expand All @@ -28,15 +29,13 @@ Signing up with an email address, Google, or GitHub account requires additional
- If you sign up with Google or GitHub, you must first verify your email address with that provider.
- If you sign up with an email address, Docker sends a verification email. Follow the procedures in that email to verify your account and complete the sign-up process.

Docker blocks sign-in until you've verified your account.
Docker blocks sign-in until you've verified your account.

### Sign up with your email

1. Go to the [Docker sign-up page](https://app.docker.com/signup/) and enter a unique, valid email address.
1. Enter a username to use as your Docker ID. Once you create your Docker ID
you can't reuse it in the future if you deactivate this account. Your username:
- Must be between 4 and 30 characters long
- Can only contain numbers and lowercase letters
you can't reuse it in the future if you deactivate this account. Your username: - Must be between 4 and 30 characters long - Can only contain numbers and lowercase letters
1. Choose a password that's at least 9 characters long, then select **Sign Up**.
1. Verify your email address when you receive the Docker verification email. This completes the registration process.

Expand All @@ -46,10 +45,10 @@ you can't reuse it in the future if you deactivate this account. Your username:
1. Select your social provider, Google or GitHub.
1. Select the social account you want to link to your Docker account.
1. Select **Authorize Docker** to let Docker access your social account
information. You will be re-routed to the sign-up page.
information. You will be re-routed to the sign-up page.
1. Enter a username to use as your Docker ID. Your username:
- Must be between 4 and 30 characters long
- Can only contain numbers and lowercase letters
- Must be between 4 and 30 characters long
- Can only contain numbers and lowercase letters
1. Select **Sign up**.

## Sign in to your account
Expand All @@ -73,7 +72,7 @@ accounts are automatically linked.

If no Docker ID exists, Docker creates a new account for you.

Docker doesn't currently support linking multiple sign-in methods
Docker doesn't support linking multiple sign-in methods
to the same Docker ID.

### Sign in using the CLI
Expand Down Expand Up @@ -108,5 +107,6 @@ If you have a paid Docker subscription,
All Docker users can seek troubleshooting information and support through the
following resources, where Docker or the community respond on a best effort
basis:
- [Docker Community Forums](https://forums.docker.com/)
- [Docker Community Slack](http://dockr.ly/comm-slack)

- [Docker Community Forums](https://forums.docker.com/)
- [Docker Community Slack](http://dockr.ly/comm-slack)
25 changes: 13 additions & 12 deletions content/manuals/accounts/deactivate-user-account.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,25 +15,26 @@ see [Deactivating an organization](../admin/organization/deactivate-account.md).
> [!WARNING]
>
> All Docker products and services that use your Docker account are
inaccessible after deactivating your account.
> inaccessible after deactivating your account.

## Prerequisites

Before deactivating your Docker account, ensure you meet the following requirements:

- If you are an organization or company owner, you must leave your organization
or company before deactivating your Docker account:
1. Sign in to [Docker Home](https://app.docker.com/admin) and choose
your organization.
1. Select **Members** and find your username.
1. Select the **Actions** menu and then select **Leave organization**.
or company before deactivating your Docker account:
1. Sign in to [Docker Home](https://app.docker.com/admin) and choose
your organization.
1. Select **Members** and find your username.
1. Select the **Actions** menu and then select **Leave organization**.
- If you are the sole owner of an organization, you must assign the owner role
to another member of the organization and then remove yourself from the
organization, or deactivate the organization. Similarly, if you are the sole
owner of a company, either add someone else as a company owner and then remove
yourself, or deactivate the company.
to another member of the organization and then remove yourself from the
organization, or deactivate the organization. Similarly, if you are the sole
owner of a company, either add someone else as a company owner and then remove
yourself, or deactivate the company.
- If you have an active Docker subscription, [downgrade it to a Docker Personal subscription](../subscription/change.md).
- Download any images and tags you want to keep. Use `docker pull -a <image>:<tag>`.
- Download any images and tags you want to keep. Use `docker pull -a <image>`
to pull all tags, or `docker pull <image>:<tag>` to pull a specific tag.
- Unlink your [GitHub and account](../docker-hub/repos/manage/builds/link-source.md#unlink-a-github-user-account).

## Deactivate
Expand All @@ -43,7 +44,7 @@ Once you have completed all the previous steps, you can deactivate your account.
> [!WARNING]
>
> Deactivating your account is permanent and can't be undone. Make sure
to back up any important data.
> to back up any important data.

1. Sign in to [Docker Home](https://app.docker.com/login).
1. Select your avatar to open the drop-down menu.
Expand Down
15 changes: 7 additions & 8 deletions content/manuals/admin/organization/deactivate-account.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: Learn how to deactivate a Docker organization and required prerequi
keywords: delete, deactivate organization, account, organization management, Admin Console, cancel subscription
weight: 42
aliases:
- /docker-hub/deactivate-account/
- /docker-hub/deactivate-account/
---

{{< summary-bar feature_name="General admin" >}}
Expand All @@ -16,15 +16,15 @@ accounts, see [Deactivate a user account](../../accounts/deactivate-user-account
> [!WARNING]
>
> All Docker products and services that use your Docker account or organization
account will be inaccessible after deactivating your account.
> account will be inaccessible after deactivating your account.

## Prerequisites

You must complete all the following steps before you can deactivate your
organization:

- Download any images and tags you want to keep:
`docker pull -a <image>:<tag>`.
- Download any images and tags you want to keep. Use `docker pull -a <image>`
to pull all tags, or `docker pull <image>:<tag>` to pull a specific tag.
- If you have an active Docker subscription, [downgrade it to a free subscription](../../subscription/change.md).
- Remove all other members within the organization.
- Unlink your [GitHub and Bitbucket accounts](../../docker-hub/repos/manage/builds/link-source.md#unlink-a-github-user-account).
Expand All @@ -38,12 +38,11 @@ Docker Hub.
> [!WARNING]
>
> This cannot be undone. Be sure you've gathered all the data you need from
your organization before deactivating it.
> your organization before deactivating it.

1. Sign in to [Docker Home](https://app.docker.com) and select the organization
you want to deactivate.
you want to deactivate.
1. Select **Admin Console**, then **Deactivate**. If the **Deactivate**
button is unavailable, confirm you've completed all [Prerequisites](#prerequisites).
button is unavailable, confirm you've completed all [Prerequisites](#prerequisites).
1. Enter the organization name to confirm deactivation.
1. Select **Deactivate organization**.

61 changes: 39 additions & 22 deletions content/manuals/ai/mcp-catalog-and-toolkit/cli.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Use MCP Toolkit from the CLI
linkTitle: Use with CLI
description: Manage MCP profiles, servers, and catalogs using the Docker MCP CLI.
description: Manage MCP profiles, servers, and catalogs using Docker MCP CLI.
keywords: docker mcp, cli, profiles, servers, catalog, gateway
weight: 35
---
Expand Down Expand Up @@ -73,12 +73,12 @@ select a server, and check the **Server ID** field.
Servers are referenced by URI. The URI format depends on where the server
comes from:

| Format | Source |
| --- | --- |
| `catalog://<catalog-ref>/<server-id>` | An OCI catalog |
| `docker://<image>:<tag>` | A Docker image |
| `https://<url>/v0/servers/<uuid>` | The MCP community registry |
| `file://<path>` | A local YAML or JSON file |
| Format | Source |
| ------------------------------------- | -------------------------- |
| `catalog://<catalog-ref>/<server-id>` | An OCI catalog |
| `docker://<image>:<tag>` | A Docker image |
| `https://<url>/v0/servers/<uuid>` | The MCP community registry |
| `file://<path>` | A local YAML or JSON file |

The most common format is `catalog://`, where `<catalog-ref>` matches the
**Catalog** field and `<server-id>` matches the **Server ID** field shown in
Expand Down Expand Up @@ -222,39 +222,53 @@ $ echo ".vscode/mcp.json" >> .gitignore

## Share profiles

Share profiles with your team using OCI registries or version control.

### Share via OCI registry

Profiles are shared as OCI artifacts via any OCI-compatible registry.
Credentials are not included for security reasons. Team members configure
OAuth separately after pulling.
authentication credentials separately after pulling.

### Push a profile
To push an existing profile called `web-dev` to an OCI registry:

```console
$ docker mcp profile push <profile-id> <registry-reference>
$ docker mcp profile push web-dev registry.example.com/profiles/web-dev:v1
```

For example:
To pull the same profile:

```console
$ docker mcp profile push web-dev registry.example.com/profiles/web-dev:v1
$ docker mcp profile pull registry.example.com/profiles/team-standard:latest
```

### Pull a profile
### Share via version control

For project-specific profiles, you can use the `export` and `import` commands
and store the profiles in version control alongside your code. Team members can
import the file to get the same configuration.

To export a profile to your project directory:

```console
$ docker mcp profile pull <registry-reference>
$ mkdir -p .docker
$ docker mcp profile export web-dev .docker/mcp-profile.json
```

For example:
Team members who clone the repository can import the profile:

```console
$ docker mcp profile pull registry.example.com/profiles/team-standard:latest
$ docker mcp profile import .docker/mcp-profile.json
```

This creates a profile with the servers and configuration defined in the
file. Any authentication credentials must be configured separately if needed.

## Custom catalogs

Custom catalogs let you curate a focused collection of servers for your team or
organization. For an overview of what custom catalogs are and when to use them,
see [Custom catalogs](/manuals/ai/mcp-catalog-and-toolkit/catalog.md#custom-catalogs).
Custom catalogs let you curate a focused collection of servers for your team
or organization. For an overview of what custom catalogs are and when to use
them, see [Custom catalogs](/manuals/ai/mcp-catalog-and-toolkit/catalog.md#custom-catalogs).

Catalogs are referenced by OCI reference, for example
`registry.example.com/mcp/my-catalog:latest`. Servers within a catalog use
Expand All @@ -267,7 +281,8 @@ Use the Docker catalog as a base, then add or remove servers to fit your
organization's needs. Copy it first:

```console
$ docker mcp catalog tag mcp/docker-mcp-catalog registry.example.com/mcp/company-tools:latest
$ docker mcp catalog tag mcp/docker-mcp-catalog \
registry.example.com/mcp/company-tools:latest
```

List the servers it contains:
Expand All @@ -279,7 +294,8 @@ $ docker mcp catalog server ls registry.example.com/mcp/company-tools:latest
Remove servers your organization doesn't approve:

```console
$ docker mcp catalog server remove registry.example.com/mcp/company-tools:latest \
$ docker mcp catalog server remove \
registry.example.com/mcp/company-tools:latest \
--name <server-name>
```

Expand Down Expand Up @@ -357,7 +373,8 @@ can find to your curated set.
To enable specific servers from your catalog without using a profile:

```console
$ docker mcp gateway run --catalog <oci-reference> --servers <name1> --servers <name2>
$ docker mcp gateway run --catalog <oci-reference> \
--servers <name1> --servers <name2>
```

## Further reading
Expand Down
11 changes: 6 additions & 5 deletions content/manuals/ai/mcp-catalog-and-toolkit/profiles.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,13 @@
weight: 25
---

{{< summary-bar feature_name="Docker MCP Toolkit" >}}
{{< summary-bar feature_name="MCP Profiles" >}}

> [!NOTE]
> This page describes the MCP Toolkit interface in Docker Desktop 4.62 and
> later. Earlier versions have a different UI. Upgrade to follow these
> instructions exactly.
> [!IMPORTANT]
> MCP Profiles is rolling out gradually in Docker Desktop 4.63. If you don't
> see the **Profiles** tab in your Docker Desktop, it hasn't been enabled for
> your account yet. It will become available to all users as the rollout

Check failure on line 14 in content/manuals/ai/mcp-catalog-and-toolkit/profiles.md

View workflow job for this annotation

GitHub Actions / validate (vale)

[vale] reported by reviewdog 🐶 [Vale.Spelling] Did you really mean 'rollout'? Raw Output: {"message": "[Vale.Spelling] Did you really mean 'rollout'?", "location": {"path": "content/manuals/ai/mcp-catalog-and-toolkit/profiles.md", "range": {"start": {"line": 14, "column": 66}}}, "severity": "ERROR"}
> completes.

Profiles organize your MCP servers into named collections. Without profiles,
you'd configure servers separately for every AI application you use. Each time
Expand Down
Loading
Loading