Bug 13051 - allow Open Container compliant "images" to be generated from oe images (container or not)
Summary: allow Open Container compliant "images" to be generated from oe images (conta...
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: deployment (show other bugs)
Version: 2.7
Hardware: All Multiple
: Medium+ enhancement
Target Milestone: 6.0 M2
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-11-30 20:26 UTC by Bruce Ashfield
Modified: 2026-03-19 16:09 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruce Ashfield 2018-11-30 20:26:24 UTC
oe-core needs to only get the minimal plumbing/capabilities, since there is no one size fits all solution to this, and many of the existing tools are far to heavy / complex for oe-core to carry (20-30 significant native and target depends/rdepends) .. this is due to broad (and deep) support in the tools, but is much more than is required for generating container images.

In fact, what oe-core needs is somewhat custom, since the existing tools are not designed to quickly create simple OCI “image”.

What is done with the image after it is generated (installed to a rootfs/image), pushed to a registry, converted to a docker compatible image, are secondary steps and are left as user specific extensions. The tools to support these manipulations are part of meta-virtualization.
Comment 1 Bruce Ashfield 2019-02-26 21:09:58 UTC
Implementation is done.

It is an open question whether or not this should go into oe-core this release, or soak for one release in meta-virt, before a proposed move to core.
Comment 2 Randy MacLeod 2019-08-15 15:09:11 UTC
Any decision on whether to move this from meta-virt to oe-core for 2.8?
Comment 3 Bruce Ashfield 2019-08-15 15:17:12 UTC
There's enough other changes going into the fall release, that this is just too much. It needs more discussion and some broader meetings, which I'll do for the 2020 spring release.

I'm moving this to 3.1 to show that, since IIRC, isn't 2.8 now 3.0 ?
Comment 4 Randy MacLeod 2019-08-15 16:20:04 UTC
Thanks Bruce. 
Yes, 2.8 now known as 3.0.
Comment 5 Bruce Ashfield 2021-03-15 19:14:36 UTC
moving these to the next release. The ground work is in meta-virt, but obviously not ready for this release.
Comment 6 Bruce Ashfield 2022-09-29 15:24:15 UTC
Still valid, moving to 4.2 so it can be coordinated with binary distro efforts.
Comment 7 Randy MacLeod 2025-04-24 18:54:45 UTC
Bulk move as requesting during YP BB meeting.
Comment 8 Bruce Ashfield 2026-03-19 16:09:57 UTC
meta-virt has everything needed to do this now.