Open zhouhao3 opened 6 years ago
ping @opencontainers/image-tools-maintainers
@coolljt0725 UI in #169 needs to be fixed: these images don't have a name, they have a tag. The API should allow for arbitrary label selection. The current situation prevents us from ever adding a name in the future. I described the desired behavior and syntax in https://github.com/opencontainers/image-tools/issues/164#issuecomment-317904913.
Something like this:
oci-image-tool validate --select annotations."org.opencontainers.ref.name"=latest --select platform.os=linux ubuntu.tar
Fine. I'll modify it.
Hi everyone, In order to achieve the release as soon as possible, I made the following roadmap, any comments are welcome. cc @opencontainers/image-tools-maintainers @wking
Currently, image-tools has implemented the following functions: 1.Validate one or more image files 2.Unpack an image or image source layout 3.Create an OCI runtime bundle
image-tools has implemented the most important verification function, so I think image-tools can already prepare v1.0 release.
The following a roadmap draft, any comments are welcome.
v1.0: Solve image-tools problems. There are two known problems with image-tools: 1.How to handle multiple manifests with the same ref.name: We discussed this problem in #164 and proposed a solution waiting for review in #169. 2.Autodetect problem: The main reason for this problem is that the main judgment in the
Autodetect
function is that the Mediatype field becomes a non-required field inspec
. So that leads to validation errors. We discussed this problem in #62 an proposed a solution waiting for review in #184 and #62 (Two different solutions).v1.x: Add additional functionality. Add create-layer sub command #8 Add create-image sub command Add oci-cas sub command #40 (This still need to discuss, the current views are not uniform.)
These above features are additional features. We can wait until later.
Most of the plans have a corresponding patch, but we need to discuss and optimize.Please come up with anything to add.