Once 9502 is finished, a further extension to that would be the ability to add docker metadata to the container image. docker metadata are items such as ENTRYPOINT, repo, imagename, etc.
At some point you've buried too much information into build meta-data, and is really isn't a flexible way to encode this sort of thing. Having done a lot of work with OCI (you should reference that, and not docker) and the configuration/launch of those containers, having that information as part of the build system really isn't all that useful. The configuration needs to be changed/modified tweaked at runtime via the container tooling anyway. See meta-overc if you are interested in the types of tweaks that I'm talking about and how they would be hard to apply to build meta-data.
To help clarify requirement, imagine a solution involving multiple containers running on a host OS communicating over an agreed protocol. This bug refers to building one (or more) of these containers, not the host OS or deciding what runs in which containers.
(In reply to comment #2) > To help clarify requirement, imagine a solution involving multiple > containers running on a host OS communicating over an agreed protocol. This > bug refers to building one (or more) of these containers, not the host OS or > deciding what runs in which containers. That actually doesn't clarify very much. Building a container is trivial, binary output of an app + dependencies, or an image + no ability to boot. Having container meta data is not the business of any build system, since it is completely variable at runtime.
Moving to M3
moving this future item to unassigned.
This should follow the OCI "labels" or "annotations" metadata format: https://github.com/opencontainers/image-spec/blob/master/annotations.md
This is important for the eclipse-yocto plugin development in process.
This basically breaks when a container is hosted on Docker hub as any custom metadata will be stripped. It is also part of a design direction that has been abandoned.