> ## 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.

# Manage Default EVE-OS Images

> How to view, set, and change the default EVE-OS image for your enterprise using ZCLI.

## Introduction

Your enterprise can designate a default EVE-OS image for each supported CPU architecture (AMD64 and ARM64). The default image is used to onboard new nodes that do not have a specific image version assigned. You can change the default at any time, but doing so does not automatically update existing nodes.

When you add an EVE-OS image to your enterprise, Edge Infrastructure Services does not automatically mark it as the default. You must set the default explicitly each time you want to designate a new version.

Default EVE-OS image management for a regular enterprise administrator is performed using ZCLI. There is no dedicated EVE-OS Images management page in the console for that role, and console image version selection appears only during node onboarding. See [Onboard Nodes](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/onboard-nodes.md#use-single-use-installer) for the onboarding flow. Cloud-service and support administrators can also set the default from the console EVE-OS Images page under Admin Dashboard > Images > EVE-OS Images.

## Prerequisites

* ZCLI running. See [Get Started With ZCLI](https://zededa.mintlify.site/zcli-reference/get-started.md) for authentication steps.
* Your enterprise must have at least one EVE-OS image. See [Add a rootfs EVE-OS Image to Your Enterprise](https://zededa.mintlify.site/new-ui/infrastructure-services/eve-os-management/add-an-eve-os-image.md).

## View the Default EVE-OS Image

1. Start a ZCLI session. See [Get Started With ZCLI](https://zededa.mintlify.site/zcli-reference/get-started.md) for authentication steps.
2. Display the default image for your target architecture.

For AMD64:

```text theme={"dark"}
zcli image show --latest=AMD64
```

For ARM64:

```text theme={"dark"}
zcli image show --latest=ARM64
```

## Set an EVE-OS Image as Default

1. Start a ZCLI session. See [Get Started With ZCLI](https://zededa.mintlify.site/zcli-reference/get-started.md) for authentication steps.
2. Mark your target image as default. Replace `IMAGE_NAME` with the version string and `AMD64_OR_ARM64` with the appropriate architecture.

```text theme={"dark"}
zcli image mark-latest IMAGE_NAME --image-arch=AMD64_OR_ARM64
```

For example:

```text theme={"dark"}
zcli image mark-latest 11.0.5-lts-kvm-amd64 --image-arch=AMD64
```

3. Verify the new default.

```text theme={"dark"}
zcli image show --latest=AMD64
```

## Remove a Default EVE-OS Image

You cannot delete an EVE-OS image while it is set as the default. To replace the default, set a different image as the default first, then delete the old image if needed.

1. Mark a different image as the new default using `zcli image mark-latest` (see the preceding section).
2. Verify the new default is set.
3. Delete the old image if needed. See [Delete an EVE-OS Image](https://zededa.mintlify.site/new-ui/infrastructure-services/eve-os-management/delete-an-eve-os-image.md).

If you attempt to delete an image that is currently set as the default, the operation fails with an error similar to:

```text theme={"dark"}
Image delete failed: Conflict
[Error DependencyConflict: Dependent Entry exists]
[Error DependencyConflict: Image 7.4.1-kvm-amd64 is marked as default image for AMD64, can't be deleted]
```

## Next Steps

> [card] [Add a rootfs EVE-OS Image to Your Enterprise](https://zededa.mintlify.site/new-ui/infrastructure-services/eve-os-management/add-an-eve-os-image.md)
>
> Upload or uplink an EVE-OS rootfs image.

> [card] [Delete an EVE-OS Image](https://zededa.mintlify.site/new-ui/infrastructure-services/eve-os-management/delete-an-eve-os-image.md)
>
> Remove an image from your enterprise.

> [card] [EVE-OS Management Overview](https://zededa.mintlify.site/new-ui/infrastructure-services/eve-os-management/eve-os-management.md)
>
> Overview of all EVE-OS image management operations.