container-registry: make IMAGE_FEATURES local to image recipes

Remove the global IMAGE_FEATURES[validitems] registration entirely.
Setting it in layer.conf or a globally-inherited bbclass changes the
varflag value, which gets pulled into the signature of every recipe
that depends on IMAGE_FEATURES — causing yocto-check-layer signature
change failures.

Image recipes that use the container-registry feature already set
IMAGE_FEATURES[validitems] locally (e.g. container-image-host.bb).
Users who want the feature in their own images add the one-liner:
  IMAGE_FEATURES[validitems] += "container-registry"

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>

1 files changed, 0 insertions, 3 deletions

diff --git a/classes/meta-virt-container-cfg.bbclass b/classes/meta-virt-container-cfg.bbclass
index f797a6aa..9a4b144e 100644
--- a/classes/meta-virt-container-cfg.bbclass
+++ b/classes/meta-virt-container-cfg.bbclass
@@ -8,6 +8,3 @@
 # match the other configs of the layer and in case the above statement isn't
 # always true in the future.
 include ${@bb.utils.contains('DISTRO_FEATURES', 'virtualization', '${META_VIRT_CONTAINER_CONFIG_PATH}', '${META_VIRT_CONTAINER_CONFIG_PATH}', d)}
-
-# Register custom IMAGE_FEATURES only when container features are enabled
-IMAGE_FEATURES[validitems] += "${@bb.utils.contains_any('DISTRO_FEATURES', 'vcontainer virtualization', 'container-registry', '', d)}"