Cross Platform Enablement for the Yocto Project with Containers
Talkat Embedded Linux Conference + OpenIoT Summit North America 2017 · on Wednesday, 2017-02-22· at 11:30· Broadway III/IV·
summary
Docker images for Yocto host a repeatable, isolated build environment that runs bitbake, toaster and the extensible SDK/devtool so a full build like core-image-minimal completes inside the container and the output lands in a bind‑mounted workdir. Containers use Linux namespaces and cgroups to prevent leaked processes; images are rebuilt weekly on Docker Hub. Workflows run on Linux, macOS (via the Docker hypervisor plus a Samba-mounted volume) and Windows 10 Pro; demo hardware used two cores and 8 GB RAM and toaster serves on port 18000.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:54THE MULTIPLE DISTRO PROBLEM
- 2:06BITBAKE SOMETIMES LEAKS PROCESSES
- 3:30CONTAINERS AREN'T MAGIC
- 6:04PID NAMESPACE EXAMPLE
- 8:20SAMPLE DOCKERFILE
- 9:28DOCKER RUN
- 15:29POKY CONTAINER DISTROS
- 33:55DIFFERENCES
- 42:29QUESTIONS?
related talks
21mMaking Reproducible Builds Faster with Docker Bake
17mGetting Rid of "It Works on my Machine"
39mListening to your Users: Refactoring the Yocto Project
28mWhat's New in Docker Build
57mExternal Pre-built Binary Toolchains
50mHowto: Options Galore to Get from Source Code to Container
47mOptimizing the Microsoft developer experience with Docker
36mClosing the Developer Experience Gap of your Container Platforms
