> ## Documentation Index > Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL. > Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other. > Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking. > Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify. # Add an Edge App Image > Upload or link a virtual machine, container, or ISO image as an Edge App image in the Build section of Edge Infrastructure Services. ## Introduction An Edge App image provides the image file or container reference for a standalone application workload on a node. You can add an Edge App image in four formats: Container (an OCI image reference pulled from a container registry), QCOW2 (a virtual machine disk image), RAW (a raw disk image), or ISO (bootable installation media). Use the format that matches the artifact you have. Use the Edge App type when you need to run a standalone workload as a virtual machine, container, or installation image on a node. After adding the image, you deploy it as an application instance on your nodes. ### Prerequisites * You have the SysManager or SysAdmin role in your enterprise. See [Manage Roles](https://zededa.mintlify.site/new-ui/infrastructure-services/administration/manage-roles.md). * For Container format: a datastore of container registry type is configured in Edge Infrastructure Services with credentials for the registry where your image is stored. * For Upload (QCOW2, RAW, or ISO): you have the image file available locally. * For Uplink (QCOW2, RAW, or ISO): you have the SHA-256 hash, file size, and a configured datastore that hosts the image. ## Open the Image Type Selector 1. In the sidebar, navigate to **Infrastructure > Workloads > Build > App Images**. 2. Click **New App Image**. 3. On the **Add Edge App Image** screen, click **Edge App**. ## Complete Image Details In the **Image Details** section, select the image format and CPU architecture. ### Select a format Click the format that matches your image: * **Container**: for OCI container images pulled from a container registry. * **QCOW2**: for QCOW2 virtual machine disk images. * **RAW**: for raw disk images. * **ISO**: for bootable ISO installation media. ### Select an architecture Select the CPU architecture the image targets: * **AMD 64**: for x86-64 images. * **ARM 64**: for ARM 64-bit images. Click **Next**. ## Provide Storage Details In the **Storage** section, define where the image comes from. The fields shown depend on the format you selected in the preceding section. ### Container format If you chose **Container** as your image format, the platform pulls the image from a container registry at deployment time. There is no upload or uplink step. Provide the registry location: 1. In the **Datastores** field, select the datastore that represents the container registry where your image is stored. 2. After selecting a datastore, enter the **Image Relative URL**: the path to the container image within the registry (for example, `myapp:1.0.0`). Click **Next**. ### Upload (QCOW2, RAW, or ISO) If you chose **QCOW2**, **RAW**, or **ISO** as your image format and want to upload a file directly from your local machine: 1. In the **Add Image Via** field, select **Upload**. 2. In the **Image Path** field, enter the file name for the image. This value is used as the image identifier on the platform. 3. Click **Choose File** and select the image file from your local machine. 4. In the **Data Store** field, select the datastore where the uploaded image will be stored. Click **Next**. ### Uplink manually (QCOW2, RAW, or ISO) If you chose **QCOW2**, **RAW**, or **ISO** as your image format and want to reference an image already stored in a datastore without uploading a file: 1. In the **Add Image Via** field, select **Uplink manually**. 2. In the **SHA256** field, enter the 64-character hexadecimal SHA-256 hash of the image file. 3. In the **Image Size** field, enter the file size and select the appropriate unit (Bytes, KB, MB, GB, or TB). 4. In the **Datastores** field, select the datastore where the image is stored. 5. After selecting a datastore, enter the **Image Relative URL**: the path to the image file within the datastore. Click **Next**. ## Complete General Information In the **General** section, provide identity information for the image. 1. In the **Name** field, enter a unique identifier. The name must be at least three characters. Use alphanumeric characters and hyphens (for example, `my-edge-app-1-0`). 2. In the **Title** field, enter a human-readable display name. The title must be at least three characters. 3. Optionally, in the **Description** field, enter a description of up to 256 characters. ## Add the Image Click **Add Image**. * If you selected **Upload**, the platform uploads the file and shows a progress bar with the upload percentage. When the upload completes, the detail page opens. * If you selected **Uplink manually** or **Container**, the platform initiates the uplink process. The image status changes to **Uplinking** while the platform fetches the file or verifies the container reference. ## Verify the Configuration After you add the image: 1. Navigate to **Infrastructure > Workloads > Build > App Images** and open the new image. 2. On the **Details** tab, confirm the format, architecture, and status are correct. The status should reach **Ready** after the upload or uplink completes. 3. On the **Source** tab, verify the SHA-256 hash and datastore association. ## Next Steps > [card] [Create and Manage an App Image](https://zededa.mintlify.site/new-ui/infrastructure-services/build-and-library/manage-an-app-image.md) > > Configure or delete the image after creation. > [card] [Manage an Application Instance](https://zededa.mintlify.site/new-ui/infrastructure-services/applications/manage-an-application-instance.md) > > Deploy the image as an application instance on a node.