---
title: Manage application releases
slug: edgemanager/lem-user-guide/deploy-applications/marketplace-catalog/available-applications/manage-application-releases
description: A Docker application release is always in one of two states, RELEASED (submitted) or DRAFT. 
docTags: 
createdAt: 2022-11-30T15:29:34.000Z
---

A Docker application release is always in one of two states, `RELEASED` (submitted) or `DRAFT`. When a Docker application release is in `RELEASED` state, it cannot be further modified. When it is in `DRAFT`, it can be modified.

:::hint{type="warning"}
**Important: **When a docker application release is in `DRAFT` state it can't be deployed to a Litmus Edge instance.
:::

See the following on how to manage Docker application releases. The following user interface is identical for *Containers*, *Containers Advanced*, and *Compose*.

:::hint{type="info"}
**Note:** If you have the **Observer** Marketplace role, you can view releases but you cannot clone, edit, submit, or remove them.
:::

![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/aet8lY4FRC5TADGHWpqZ7_2023-07-2111-15-43.png "Containers/Containers Advanced/Compose")

| **Action**                                    | **Details**                                                                                                                                                                                                               |
| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| \[1] **Clone release**                        |  Search by *Name*, *Image*.                                                                                                                                                                                               |
| \[2] **Show release details **           | Modifications cannot be made when viewing a submitted release.                                                                                                                                                            |
| \[3]  **Remove release **                | - Removing a release cannot be undone.                                                                                                                                                                                    |
| \[4] **View more details about this release** | See [Set Up Variables for an Application Release](docId\:Vub4oJVy40nXIZdpR7GLh) and [Set Up Docker Container Configurations for an Application Release](docId\:bv7rrzQjjyNwEEeOWyHzV) for details.                        |
| \[5] **Edit release &#x20;**                  | Once a release has been submitted, you can no longer modify it. You can clone the submitted release, and then modify the clone (while it is still in the Draft status).<br />- **Edit Release**<br />- **Submit Release** |

## Clone a release

Clone a release to create a draft copy that you can modify. You can clone a submitted release.

**To clone a release:**

1. Find the release that you want to clone.
2. On the release tile, click **Clone**. The *Clone Release* dialog box appears.
3. In **New Release Name**, enter a name for the new release. The name must be unique for the application and can have up to 32 characters. The first character must be an ASCII letter, a digit, or an underscore `_`. The remaining characters can be ASCII letters, digits, underscores `_`, periods `.`, or hyphens `-`.
4. Click **Clone**. If the name is not valid, an error message appears and the clone is not created.

The clone opens in the DRAFT state.

:::hint{type="info"}
**Note:** If a submitted release contains a short-syntax port mapping with a variable, such as `${UI_PORT}:3130`, and you submitted it before the fix, clone the release and submit the clone. See Configure container settings.
:::

## Next steps

After a Draft Application Release has been submitted (`RELEASED`), it can then be deployed to Litmus Edge instances. See [Deploy an Application to Edge Devices](docId\:LPoLphiKImgS3lab4OrjK) for details.