Bug 13052 - Allow oe-core generated OCI containers to be executed/tested on the build host
Summary: Allow oe-core generated OCI containers to be executed/tested on the build host
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.7
Hardware: All Multiple
: Medium+ enhancement
Target Milestone: 6.0 M3
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-11-30 20:39 UTC by Bruce Ashfield
Modified: 2026-05-28 14:29 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:39:26 UTC
The prerequisite for this feature is bugzilla 13051

Similar to how "runqemu" executes full images, application and system containers generated via oe-core can be executed using runc/docker on the build host. This is purely for testing userspace and container compatibility before they are pushed to a registry, etc. 

Of course the host/container architecture must match, and the default networking of the container engine must be sufficient.
Comment 1 Bruce Ashfield 2019-02-26 21:09:02 UTC
Implementation done. Will submit to meta-virtualization this release, and then propose a move to oe-core in the fall.
Comment 2 Bruce Ashfield 2022-09-29 15:22:31 UTC
Still valid, moving to 4.2 so it can be coordinated with binary distro efforts.
Comment 3 Randy MacLeod 2024-10-17 19:04:15 UTC
Bulk move of medium importance bugs from 5.1 to 5.2 on behalf of Bruce.
Comment 4 Bruce Ashfield 2026-05-28 14:29:10 UTC
meta-virtualization vdkr/vpmn provide this functionality.