Bug 9503

Summary: Add a way to add docker metadata to container images
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Randy Witt <randy.e.witt>
Component: coreAssignee: Unassigned <unassigned>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: Medium+ CC: bluelightning, brian.avery, bruce.ashfield, ee.peng.yeoh, henry.bruce, joshuagloe, meta.mr.watcher, meta.watcher, randy.macleod, tim.orling
Version: 2.1   
Target Milestone: 4.99   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)
Bug Depends on: 9502    
Bug Blocks:    

Description Randy Witt 2016-04-21 16:24:57 UTC
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.
Comment 1 Bruce Ashfield 2017-05-03 16:19:28 UTC
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.
Comment 2 Henry Bruce 2017-05-22 20:52:49 UTC
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.
Comment 3 Bruce Ashfield 2017-05-23 00:39:54 UTC
(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.
Comment 4 brian avery 2017-07-30 13:32:17 UTC
Moving to M3
Comment 5 brian avery 2017-12-08 21:38:17 UTC
moving this future item to unassigned.
Comment 6 Tim Orling 2018-03-22 16:13:41 UTC
This should follow the OCI "labels" or "annotations" metadata format:
https://github.com/opencontainers/image-spec/blob/master/annotations.md
Comment 7 Tim Orling 2018-03-22 16:14:45 UTC
This is important for the eclipse-yocto plugin development in process.
Comment 8 Tim Orling 2020-06-25 08:15:31 UTC
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.