Home Explore Blog Models CI



docker

1st chunk of `content/manuals/extensions/extensions-sdk/extensions/validate.md`
093f599574d293a9bbd9d72c1f6a34af5313bdd80f92bc05000000010000059e
---
title: Validate your extension
linkTitle: Validate
description: Step three in the extension creation process
keywords: Docker, Extensions, sdk, validate, install
aliases:
 - /desktop/extensions-sdk/extensions/validation/
 - /desktop/extensions-sdk/build/build-install/
 - /desktop/extensions-sdk/dev/cli/build-test-install-extension/
 - /desktop/extensions-sdk/extensions/validate/
weight: 20
---

Validate your extension before you share or publish it. Validating the extension ensures that the extension:

- Is built with the [image labels](labels.md) it requires to display correctly in the marketplace
- Installs and runs without problems

The Extensions CLI lets you validate your extension before installing and running it locally.

The validation checks if the extension’s `Dockerfile` specifies all the required labels and if the metadata file is valid against the JSON schema file.

To validate, run:

```console
$ docker extension validate <name-of-your-extension>
```

If your extension is valid, the following message displays:

```console
The extension image "name-of-your-extension" is valid
```

Before the image is built, it's also possible to validate only the `metadata.json` file:

```console
$ docker extension validate /path/to/metadata.json
```

The JSON schema used to validate the `metadata.json` file against can be found under the [releases page](https://github.com/docker/extensions-sdk/releases/latest).

Title: Validating Docker Extensions
Summary
Before sharing or publishing a Docker extension, it's crucial to validate it to ensure it's built correctly with the required image labels and installs/runs without issues. The Extensions CLI offers a `validate` command to check the extension's `Dockerfile` for necessary labels and the `metadata.json` file against its JSON schema. Validation can be performed on the entire extension image or just the `metadata.json` file.