web UI supports importing OCI-format images but oci-cli does not
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 669
- Forks
- 236
- Avg merge
- 1m
- Merged PRs (30d)
- 4
Description
In the below example you can see how the web UI supports importing OCI-format images.
These are effectively tarballs containing:
image_metadata.jsoncontaining various useful metadataoutput.QCOW2the actual image as a qcow format disk
But this is not possible in the CLI - only VMDK and QCOW2 formats are supported.
Can we have this added please, along with some improved docs on how to use this?
Having this functionality exposed in the CLI makes it much easier to upload images, and
the metadata file already contains settings, so we don't need to make additional API
calls to modify it again later.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the CLI paths that currently accept VMDK and QCOW2 images, then compare them with the web UI's OCI import flow. Use the described image_metadata.json and output.QCOW2 contents to determine the expected inputs. Done means OCI-format tarballs can be imported through the CLI and the usage documentation explains the workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, cloud, documentation, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100