Docker Container Installs from Yocto

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.

RPI 3 Application Container built with Yocto

Deploying Image built from Dockerfile I provisioned my RPI 3 with resin-os downloaded from 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".

Using Yocto Project for Docker FROM scratch

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.

Valentine's Day for Jenkins

Using Docker - No plugins required Last time I investigated using Docker inside the “master” container. It was pretty cool, but it was inconvenient when directories needed to be mounted to the containers. I intend to continue investigating the Docker plugins, but I felt like Jenkins needed some company for Valentines Day. Jenkins JNLP Slaves as Docker Containers The goal is to add a “Normal” Jenkins slave node that can connect to the master in the typical fashion.

Brothers of Jenkins

Avoid Docker-in-Docker Using Docker-in-Docker for your CI or testing environment? Think twice. by @jpetazzo explains why the DinD approach is bad for CI, and how using an alternative approach will allow the docker container to create sibling containers rather than child containers. Modifying my Docker setup I need to install docker into in a layer on top of the standard Jenkins image. @mjuuso has already demonstrated this in getintodevops/jenkins-withdocker and there is an associated blog post (The simple way to run Docker-in-Docker for CI).

Hiring a Ephemeral Butler

Clean up, before I get messy I have been running a lot of different docker containers, and often forgetting to use --rm. So I pruned my system: docker system --prune as recommended by this answer on StackOverfow. Starting Simple I followed the steps outlined on jenkinsci. I used the command below to get the password from the master container I just started. docker exec -it $(docker container ls -l --format "{{.

Resin CLI and Beaglebone

Getting started with the CLI I attempted to install the npm package but my system was incompatible with some of the requirements. Thankfull, rather than having to debug this issue I was able to simply download a release that I was able to simply unzip, add to path and use. Changing applicaton code, building and deploying to device The other day I deployed this application but one thing I noted was that the public url did not provde access to my API.

My Doorman, Docker Doug

I recently added a new member to my team. Doug is a Raspberry Pi that lives near my router. Unfortunately Doug will not quite open my door for me (yet) but he will notify me when my door opens or my door closes. The entire process is very flexible, but is a team effort. How does Doug do it? Doug uses a reed switch to detect if the door is open or closed.