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.
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.
Getting Started With Raspberry Pi 3 and Python Getting Started With Raspberry Pi 3 and Python NGenetzky/simple-server-python Following their guide is very easy. I was really impressed by the feedback when using git push. It shows the log messages for building the image on the build server.
└─> git push rpi3app1 master Counting objects: 62, done. Delta compression using up to 8 threads. Compressing objects: 100% (32/32), done.
More complicationed application Earlier today I deployed a application to my rpi3 that started from an example project provided by Resin.io, but now I would like to explore converting an existing application that is a little more complex.
Swagger Petstore This is a sample Petstore server. You can find out more about Swagger at http://swagger.io or on irc.freenode.net, #swagger.
Swagger Codegen from OpenAPI OpenAPI-Specification NGenetzky/ngenetzky-petstore swaggerhub/ngenetzky-petstore I revisted an old project that explored the capability to generate code from a config file describing an API.
Find my pi Find your Raspberry Pi’s IP Address Use ifconfig to find my dev machine ip use nmap to scan the computers on my network. jumpnow Building Raspberry Pi Systems with Yocto prebuilt image First I am going to load the prebuilt image.
Downloaded. Extracted using xz. Copy to sdcard using dd. This image is a whopping 2Gb! I think I am going to go straight to building my own with Yocto.
Static Website Powered by the Academic theme for Hugo.
This will hold firmware for micro controllers sold by particle.io for use with wifi or cellular cloud devices.