Saving Images
orka3 vm save Save a new image from a running VM. This saves the file system and the state of the OS, including any running applications. You can preserve the original image and deploy new VMs with the applied changes from the new image. 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
orka3 image list NEW_IMAGE_NAME. This operation does not affect the original image of the VM. This operation restarts the VM.
Syntax:
orka3 image list IMAGE_NAME. This operation restarts the VM.
Syntax:
Pushing to OCI Registries
orka3 vm push (Apple silicon-only) The state of a running VM is saved on the host and pushed to an OCI-compatible registry. The provided image must be in the following format:server.com/repository/image:tag. The :tag portion is optional and defaults to latest if not provided.
Requirements:
- Registry credentials must exist in the same namespace as the VM
- This is an async operation. To check the status:
orka3 vm get-push-status JOB_NAME
Resizing VM Disks
orka3 vm resize Resize the disk of a running VM; but only increase the size of the disk. Architecture-Specific Behavior:- For Apple silicon-based VMs (arm64): Nothing is needed after the command completes
- For Intel-based VMs (amd64): Provide SSH access credentials for Orka to complete the resize and repartition automatically. If not provided, it must be completed manually
Power Operations (Intel Only)
Note: Power operations are only available for Intel-based VMs. Stopped or suspended VMs appear as ‘Running’ when listed withorka3 vm list.
orka3 vm start
Power ON a stopped VM. The orka3 vm stop and orka3 vm start sequence acts as a VM reboot.
Syntax:
orka3 vm stop and orka3 vm start sequence acts as a VM reboot.
Syntax:
orka3 vm suspend and orka3 vm resume sequence acts as putting the VM on hold then resuming it.
Syntax: