Yocto Application Containers from SCRATCH Yesterday I wrote about Using Yocto Project for Docker FROM scratch , but I quickly realized it is hard to iterate quickly with this workflow. As I added support for python-connexion I generated a fresh container image at least 10 times. This is silly when I am only altering a few packages on the system, and so I looked to improve my workflow.
Currently I run the application containers using docker-compose.
Deploying Image built from Dockerfile I provisioned my RPI 3 with resin-os downloaded from resin.io and it automatically loaded my existing application on first boot. I want to make sure the docker images are as similar as possible; so I slightly modified the dockerfile and pushed the changes to resin which will handle deploying to my devices.
resin-os v2.10.1 resin/armv7hf-supervisor v6.6.3 Deploying Application Image built with Yocto Project I followed the steps outlined in my last post (Using Yocto Project for Docker FROM scratch) but used the ‘rpi3’ project which uses a different bsp layer and sets the machine for rpi3: MACHINE = "raspberrypi3".
Yocto and Docker Yocto Project is an amazing way to build a Linux System from the ground up. It uses an amazing build system that can build and install practically any application.
Docker is an amazing tool for running applications. There are many parts to docker, but the one that I would like to focus on is the concept of a docker image. There are standard images created for all the major distributions and its easy to create your own.