Understanding Orka images
Images are used to spin up VMs in Orka. An image contains the macOS operating system, applications, and any configurations you’ve set up. Image architecture types- amd64 architecture - Intel-based images (previously denoted by an
.imgextension) - arm64 architecture - Apple silicon-based images (previously denoted by an
.orkasiextension)
Extensions are no longer required as part of an image name. The architecture is determined automatically.
Local image commands
orka3 image list
List the locally stored images in your Orka cluster. (Note, you may not have any images until you runimagecache or a vm deploy command)
Syntax:
--output is not set, prints only essential information in a table format. Use wide for additional error information or json for JSON output.
Examples:
orka3 image copy
Copy the specified image and set a new name for the copy. Image name requirements:- Does not exceed 63 characters including the file extension (if set)
- Consists of lowercase alphanumeric characters, dashes (-) or periods (.)
- Must be unique to the cluster
Copying an image is an async operation. To check the status:
orka3 image list IMAGE_COPY_NAMEorka3 image generate
(Intel-only) Generate a new empty image with the specified size. Use an empty image to perform a fresh macOS install from ISO. Generated images are always created as amd64 images (Intel-based images) and are accessible from all namespaces.Generating an image is an async operation. To check the status:
orka3 image list GENERATED_IMAGE_NAMEorka3 image set-description
Set a custom description for the specified image. This can be helpful to identify the owner of the image, where it originated from, or how it is used across workflows. Syntax:orka3 image delete
Delete the specified locally stored images. Syntax:Image cache commands
Manage images stored on Orka cluster nodes. By adding images to a node before deployment of a VM using that base image, you can manage and control the delay caused by remote or even local cluster storage image pulls, providing consistent deployment times.Image cache operations are only supported for Apple silicon nodes. The alias for
imagecache is ic.orka3 imagecache add
Cache the specified image on the specified node(s). Add an image to one, a select number, or all cluster node namespace members or members of a tagged node group. The image must be pulled in the cluster before caching it on the node(s), unless it is an OCI image. For OCI images, make sure you have the necessary credentials to pull the OCI image.Caching an image is an async operation. To check the status:
orka3 imagecache info IMAGE_NAME--nodes, --tags, and --all flags are mutually exclusive.
Syntax:
orka3 imagecache info
Display the caching status of an image across nodes. Use this to verify if images are available for deployment (“ready” status) or if the caching operation is still active (“caching” status). Syntax:orka3 imagecache list
List cached images across nodes. Provides information about cached images such as image tag (OCI repo pulled images only), the image-id (a unique identifier from manifest), the sparse size of the image, and the number of nodes the image is cached on. Syntax:Remote images (deprecated)
orka3 remote-image list
List the available images in the remote repository or look for specific images in the remote repository. Syntax:orka3 remote-image pull
Copy an image from the remote repository and store it locally in the Orka cluster. You can keep the original name or set a new name in the local cluster storage.Pulling a remote image is an async operation. To check the status:
orka3 image list PULLED_IMAGE_NAME
