Embedded Containers as a Deployment Component via the Yocto Project
summary
Claims that the Yocto Project can produce reproducible, traceable container artifacts and use them as deployment and update units on embedded/edge devices, and demonstrates it working on a qemu x86_64 image (kernel 5.19). Uses podman + podman-tui to run a third‑party banner container and a Yocto-built curl OCI image built with meta-virtualization via bitbake, pushed to Docker Hub, pulled, run and updated via tags (latest vs easy), proving the workflow end-to-end.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:39Increased compute power Need to leverage modern / deep software stacks Orchestration/control / updates at scale • Usability for application developers • Meeting point of cut-down general purpose and customized/embedded distributions
- 4:51Flexibility to address requirements of different verticals: - networking, automotive, etc • The footprint of a container runtime can be tailored to the device - Not 'one size fits all' Application(s) can be streamlined or largely unchanged
- 11:23Who needs ? - Application and/or system developers backed by the build system and/or SDK . Who created? - The Yocto Project provides traceability who and how the container was created Creation depends on the use case test? debug? devops?
- 14:51What are containers used for on an embedded device? • What are the contents of a container? • What container runtime? • What Cloud Native Framework?
- 15:32Containers can be used for deployment, security/isolation, update, maintenance, application or system.. • Contents ? - The Yocto Project has artifacts detailing the
- 18:15Platform flexibility and standards based approach - Containers can run anywhere from the edge, to the core, to a small embedded device • Yocto Project created containers can run (almost) anywhere Whether or not the platform was built using the
- 20:22Containers can be part of any phase of embedded development - development, debug, test, etc. • Containers can be baked into the image, used for update - locally provided or fetched remotely • Containers can co-exist with Yocto project image creation, package feeds, binary artifacts - There's no need to 'choose' and exclude viable
- 24:35Isn't it all about the application? - Why care about building from source? • Solves problems you don't (yet) know you have -Evolving (think SBOM) Standards compliant and compatible • Building block technologies - Choice: don't pick winners and don't lock in Flexibility: Elements of the solution are spread
related talks
40mI heart the Yocto Project
40mWhy the Yocto Project for My IoT Project
01h 03mGetting started with Yocto Project
33mBuilding Secure & Reliable Edge Images Using RHEL for Edge Blueprinting & OSTree
37mContainer life cycle management in Automotive/Edge deployments.
45mBuilding and Maintaining Binary Distributions with Yocto
36mLessons Learned: Migrating a Production Platform to Yocto
30mYocto for open source embedded systems development