Hints for kdocker in main

Warnings

• asv-screenshot-no-media
  kdocker.appdata.xml:23 -
  A screenshot must contain at least one image or video in order to be useful. Please add an <image/> to it.
• asv-metainfo-invalid-icon-type
  kdocker.appdata.xml:17 - local
  Metainfo files may only contain icons of type `stock` or `remote`, the set type is not allowed.
• asv-metainfo-invalid-icon-type
  kdocker.appdata.xml:15 - cached
  Metainfo files may only contain icons of type `stock` or `remote`, the set type is not allowed.
• asv-cid-desktopapp-is-not-rdns
  kdocker.appdata.xml:3 - kdocker.desktop
  The component ID is not a reverse domain-name. Please update the ID to avoid future issues and be compatible with all AppStream implementations. You may also consider to update the name of the accompanying .desktop file to follow the latest version of the Desktop-Entry specification and use a rDNS name for it as well. In any case, do not forget to mention the new desktop-entry in a <launchable/> tag for this component to keep the application launchable from software centers and the .desktop file data associated with the metainfo data.
• no-metainfo
  This software component is missing a MetaInfo file to provide metadata about it.
  We currently took some data from its .desktop file and the long description of the package it is located in.
  This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.
  Additionally, a lot of software from .desktop files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be properly tagged via MetaInfo files.
  Please consider to either hide this .desktop file from AppStream by adding a X-AppStream-Ignore=true field to its .desktop file, or to write a MetaInfo file for this component and send it upstream.
  Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software will vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers).
  You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug upstream.