Open praveenkumar opened 2 years ago
Having bundle type (podman, okd, ...) as a label will also be useful.
Having bundle type (podman, okd, ...) as a label will also be useful.
@cfergeau is there any use of those currently or just to have as part of metadata?
Having bundle type (podman, okd, ...) as a label will also be useful.
@cfergeau is there any use of those currently or just to have as part of metadata?
The idea was to be able to support docker://quay.io/myorg/my-bundle:2.7.1
and to be able to build the bundle path/name (`crc_podman_libvirt_4.1.1) from this URL. However, version/bundle type is being addressed differently in https://github.com/code-ready/snc/pull/569 if I understand correctly?
Having bundle type (podman, okd, ...) as a label will also be useful.
@cfergeau is there any use of those currently or just to have as part of metadata?
The idea was to be able to support
docker://quay.io/myorg/my-bundle:2.7.1
and to be able to build the bundle path/name (`crc_podman_libvirt_4.1.1) from this URL. However, version/bundle type is being addressed differently in #569 if I understand correctly?
@cfergeau Right, when I was trying to implement it, I observe it is better to just add the bundle name as it is because this we can then directly match with bundle path/name
instead creating this details from 2-3 different metadata values (bundle-type, version, hypervisor ..etc.)
We should have a way to identify which bundle version is part of a container image without pulling it and one way to do it to add label to it so that with
skopeo inspect --no-tags docker://quay.io/crcont/podman-bundle:2.7.1
provide us this info.Currently we get following