Process<\/h2>\n\n\n\nPrerequisites<\/h3>\n\n\n\n
Yocto is a build, not a distribution, so it is quite resource intensive. I would suggest having at least 60GB free disk space, and a quad core machine at a minimum. You’ll also need a Linux installation, and the build essentials installed (git, gcc, etc.). <\/p>\n\n\n\n
EDIT: Checking the disk usage after the builds shows around 55GB used. On a 2C4T Intel Core i5 it took about 2H to build. <\/strong><\/p>\n\n\n\n First, create a working directory and clone all the piece-parts we need to build. <\/p>\n\n\n Next create the project and add the base layers.<\/p>\n\n\n Edit the conf\/local.conf file sections as needed:<\/p>\n\n\n Next we will build the image. This will take a while depending on how beefy your build machine is.<\/p>\n\n\n After a couple of hours, you will have a completed, ready to flash SD Image at <build>\/rpi3bplus-build-yocto\/rpi64\/tmp\/deploy\/images\/raspberrypi3-64\/core-image-minimal-raspberrypi3-64.rpi-sdimg<\/em> which you can burn to an SD card with:<\/p>\n\n\n Your image should boot up and docker will be running! <\/p>\n\n\n\n NOTE: You will manually have to set the date to pull from Docker registries over HTTPS because the certification validation will fail otherwise. We could add and configure NTP to fix the but… for another day.<\/strong> Use:<\/strong><\/p>\n\n\n There is one last thing you’ll want to do. You’ll want to use GParted or similar tool to enlarge your filesystem partition to take up the rest of your SD card so you will have some room for container images. You need to do this because the default SD Image builder script only provides enough space for the root filesystem and no more. In my configuration it ended up being ~300MB, so I expanded it take up the remaining ~59GB. See example below:<\/p>\n\n\n\n As it turns out, I have a system that can build and run 64-bit Docker images and is pretty darn slim. Here’s a screenshot of htop<\/em> running.. only 12 processes – not bad!<\/p>\n\n\n\n The is the minimal image and it has 12 processes, with an incredibly low footprint. I loaded up an Ubuntu container and installed iperf3, then ran a test to my laptop. I was impressed to find the following result:<\/p>\n\n\n Even running that test, the load on the Pi was:<\/p>\n\n\nProject Setup<\/h3>\n\n\n\n
\nmkdir rpi3bplus-build-yocto\ncd rpi3bplus-build-yocto\ngit clone git:\/\/git.yoctoproject.org\/poky\ngit clone git:\/\/git.openembedded.org\/meta-openembedded\ngit clone git:\/\/git.yoctoproject.org\/meta-raspberrypi\ngit clone git:\/\/git.yoctoproject.org\/meta-virtualization \n<\/pre><\/div>\n\n\n
\nsource poky\/oe-init-build-env rpi64\nbitbake-layers add-layer ..\/meta-raspberrypi\nbitbake-layers add-layer ..\/meta-openembedded\/meta-oe\nbitbake-layers add-layer ..\/meta-openembedded\/meta-python\nbitbake-layers add-layer ..\/meta-openembedded\/meta-perl\nbitbake-layers add-layer ..\/meta-openembedded\/meta-networking\nbitbake-layers add-layer ..\/meta-openembedded\/meta-filesystems\nbitbake-layers add-layer ..\/meta-virtualization\n<\/pre><\/div>\n\n\n
\nMACHINE ??= "raspberrypi3-64"\nCORE_IMAGE_EXTRA_INSTALL += "kernel-modules htop openssh iperf3 docker-ce bash ntp "\n\nINHERIT += "extrausers"\n\nEXTRA_USERS_PARAMS += " useradd pi; \\\n usermod -p 'raspberry' pi; \\\n usermod -a -G sudo pi; \\\n usermod -P root root; "\n\nDISTRO_FEATURES_append = " virtualization"\n\n<\/pre><\/div>\n\n\n
\nbitbake core-image-minimal\nParsing recipes: 100% |########################################################################################################################################################################################################| Time: 0:02:16\nParsing of 2540 .bb files complete (0 cached, 2540 parsed). 3827 targets, 140 skipped, 0 masked, 0 errors.\nNOTE: Resolving any missing task queue dependencies\n\nBuild Configuration:\nBB_VERSION = "1.44.0"\nBUILD_SYS = "x86_64-linux"\nNATIVELSBSTRING = "universal"\nTARGET_SYS = "aarch64-poky-linux"\nMACHINE = "raspberrypi3-64"\nDISTRO = "poky"\nDISTRO_VERSION = "3.0"\nTUNE_FEATURES = "aarch64 cortexa53 crc"\nTARGET_FPU = ""\nmeta \nmeta-poky \nmeta-yocto-bsp = "master:6bb4a252199cfd5d44ad7ab6fc4118c80a1aae92"\nmeta-raspberrypi = "master:a0a5d3848e76b7f90ef8e42c56211da78db1c7ba"\nmeta-oe \nmeta-python \nmeta-perl \nmeta-networking \nmeta-filesystems = "master:d9f3e6dbed8e5d96f2069280f0a566af89afb2fa"\nmeta-virtualization = "master:5fb77ae4c4e1015e40257f9e59e16c497e30c53c"\n\n<\/pre><\/div>\n\n\n
\ndd if=.\/core-image-minimal-raspberrypi3-64.rpi-sdimg of=\/dev\/sdX status=progress\n<\/pre><\/div>\n\n\n
\ndate "+%d-%m-%C%y %H:%M:%S" -s "2019-12-22 00:30:01"\n<\/pre><\/div>\n\n\n
![\"\"](\"https:\/\/jacobncalvert.com\/wp-content\/uploads\/2019\/12\/Screenshot-2019-12-21-234142.png\")
<\/a><\/figure>\n\n\n\nResults<\/h2>\n\n\n\n
![\"\"](\"https:\/\/jacobncalvert.com\/wp-content\/uploads\/2019\/12\/Screenshot-2019-12-22-000853.png\")
<\/a><\/figure>\n\n\n\nSome Metrics<\/h3>\n\n\n\n
\n[ ID] Interval Transfer Bandwidth Retr\n[ 5] 0.00-10.13 sec 116 MBytes 96.0 Mbits\/sec 9 sender\n[ 5] 0.00-10.13 sec 113 MBytes 93.8 Mbits\/sec receiver\n\n<\/pre><\/div>\n\n\n
\nroot@raspberrypi3-64:~# cat \/proc\/loadavg \n0.05 0.22 0.19 1\/141 2125\nroot@raspberrypi3-64:~# \n\n<\/pre><\/div>\n\n\n
Downloads<\/h2>\n\n\n\n