Image Registry
The dashboard's record of which images exist, where their portable artefacts live, and which clouds have promotions of each. Build a portable VHD with Packer (or capture an existing instance), Register it here, then Promote to any cloud you need it in — the dashboard runs the cross-cloud conversion + import in a transient runner inside the target cloud so the dashboard host stays out of the heavy lifting.
How cross-cloud promote works
AWS / Azure / GCP / OCI"] --> export["Native export to
same-cloud storage"] export -- "same-backend as hub
(no copy)" --> hub[("Hub backend
S3 / Blob / GCS")] export -- "different cloud
(cross-backend copy)" --> hub hub -- "presigned URL" --> runner["Target-cloud runner
ECS / ACI / Cloud Run"] runner -- "qemu-img convert
+ upload" --> staging[("Target-cloud staging")] staging --> imp["Cloud import API
ec2.ImportImage
images.create_or_update
images.insert"] imp --> ami["Native image
AMI / Managed Image / Custom Image"] ami --> promo["RegisteredImage.promotions"] style hub fill:#e0e7ff style ami fill:#d1fae5
| Name / version | Source | Promoted to | Created | Actions |
|---|---|---|---|---|
|
:
|
Register an existing image
The cloud-native ID of the existing image — what the deploy form would launch.
Where the portable VHD/RAW lives if you've exported one. Lets the promote flow re-import without rebuilding.
Promote
Source: ()
Resolve the failing checks before running the manual steps — they will block the import.
Promote runs the conversion + cloud-side import in the target cloud's own runner (ECS for AWS, ACI for Azure, Cloud Run for GCP). The dashboard returns a Job ID and opens the job page so you can watch progress. Use Show manual steps if your dashboard credentials can't reach the target.
The promotion is recorded as manual in the registry. Run the commands above; when the resulting image is in place, click Promote again on this image to retry the automated path (or update the promotion record directly via the API).