# pull

The cldkctl registry artifact pull command retrieves an artifact and its associated data from the container registry. This allows users to download a specific artifact version, including its metadata, tags, and labels, to a local environment.

## Usage

```
cldkctl registry artifact pull [artifact ID] [tag] [flags]
```

## Steps

Follow the steps below to run and view the result of this command:

1. Ensure that you are logged in. Refer to the Registry Login section.
2. Identify the Artifact ID you want to download. Refer to the Registry Artifact List section.
3. Specify the tag if you want to pull a specific version of the artifact.
4. Run the following command in your terminal:

```
cldkctl --registry [registry name] registry artifact pull [artifact ID] [tag]
```

5. Replace `[registry name]` with the target registry, `[artifact id]` with the desired artifact ID, and `[tag]` with the version tag if needed.
6. Once successful, the terminal displays **"✓ Artifact pulled successfully".**

<figure><img src="/files/bLw3M3pxZwH84H5rheAY" alt=""><figcaption></figcaption></figure>

## Flags

{% hint style="info" %}
This command supports [global flags](/cloudeka-api-list/global-flags.md). Refer to the Global Flags section for details.
{% endhint %}

| Flag       | Description                                  |
| ---------- | -------------------------------------------- |
| -h, --help | Help for the registry artifact pull command. |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudeka.ai/cloudeka-api-list/command-reference/cldkctl-registry/artifact/pull.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.