Balena base images
balenalib is the central home for 26000+ IoT focused Docker images built specifically for balenaCloud and balenaOS. This set of images provide a way to get up and running quickly and easily, while still providing the option to deploy slim secure images to the edge when you go to production.
- Multiple Architectures:
- Multiple Distributions:
- Multiple language stacks:
buildvariants designed for multistage builds.
- cross-build functionality for building ARM containers on x86.
- Helpful package installer script called
install_packagesinspired by minideb.
How to Pick a Base Image
When starting out a project, it's generally easier to have a "fatter" image, which contains a lot of prebuilt dependencies and tools. These images help you get setup faster and work out the requirements for your project. For this reason, it's recommended to start with
-build variants, and as your project progresses, switch to a
-run variant with some docker multistage build magic to slim your deploy image down. In most cases, your project can just use a Debian based distribution, which is the default if not specified, but if you know the requirements of your project or prefer specific distros, Ubuntu, Alpine, and Fedora images are available. The set of
balenalib base images follow a simple naming scheme described below, which will help you select a base image for your specific needs.
How the Image Naming Scheme Works
With over 26000
balenalib base images to choose from, it can be overwhelming to decide which image and tag are correct for your project. To pick the correct image, it helps to understand how the images are named as that indicates what is installed in the image. In general, the naming scheme for the
balenalib image set follows the pattern below:
<hw>is either architecture or device type and is mandatory. If using Dockerfile.templates, you can replace this with
%%BALENA_ARCH%%. For a list of available device names and architectures, see the Device types.
<distro>is the Linux distribution. Currently there are 4 distributions, namely Debian, Alpine, Ubuntu and Fedora. This field is optional and will default to Debian if left out.
<lang_stack>is the programming language pack, currently we support Node.js, Python, OpenJDK and Go. This field is optional, and if left out, no language pack will be installed, so you will just have the distribution.
In the tags, all of the fields are optional, and if they are left out, they will default to their
<lang_ver>is the version of the language stack, for example, Node.js 10.10, it can also be substituted for
<distro_ver>is the version of the Linux distro, for example in the case of Debian, there are 4 valid versions, namely
- For each combination of distro and stack, we have two variants called
build. The build variant is much heavier as it has a number of tools preinstalled to help with building source code. You can see an example of the tools that are included in the Debian Stretch variant here. The
runvariants are stripped down and only include a few useful runtime tools, see an example here. If no variant is specified, the image defaults to
- The last optional field on tags is the date tag
<yyyymmdd>. This is useful for production deployments as these base images are non-moving tags, so no packages in these will update ever.
<hw>: raspberrypi3 - The Raspberry Pi 3 device type.
<distro>: omitted, so it defaults to Debian.
<lang>: node - the Node.js runtime and npm will be installed
<lang_ver>: 10.18 - This gives us Node.js version 10.18.x whatever is the latest patch version provided on balenalib
<distro_ver>: omitted, so it defaults to
(build|run): omitted, so the image defaults to the slimmed down
<yyyymmdd>: omitted, we don't have a date frozen image, so new updates pushed to our 10.18 tag, for example patch versions from Node.js will automatically be inherited when they are available.
<hw>: i386 - the intel 32 bit architecture that runs on Intel Edison
latestpoints to the latest Python 2 version, which currently is 2.7.17
<distro_ver>: bionic is Ubuntu 18.04
build- to include things like
<yyyymmdd>: 20191029 is a date frozen image - so this image will never be updated on Docker Hub. Pinning to a date frozen base image is a good idea if you are running a fleet in production and are sensitive to dependencies updating and/or bandwidth constrained.
run vs. build
For each combination of
<lang> there is both a
run and a
build variant. These variants are provided to allow for easier multistage builds.
run variant is designed to be a slim and minimal variant with only runtime essentials packaged into it. An example of the packages installed in can be seen in the
build variant is a heavier image that includes many of the tools required for building from source such as
gcc, etc. As an example, you can see the types of packages installed in the
balenalib/armv7hf-debian:build variant here.
These variants make building multistage projects easier, take for example, installing an I2C node.js package, which requires a number of build time dependencies to build the native
i2c node module, but we don't want to send all of those down to our device. This is the perfect time for multistage builds and to use the
FROM balenalib/raspberrypi3-debian-node:10.10-stretch-build as build RUN npm install --only=production i2c # The run time container that will go to devices FROM balenalib/raspberrypi3-debian-node:10.10-stretch-run # Grab our node modules for the build step COPY --from=build ./node_modules ./node_modules COPY main.js main.js CMD ["node", "main.js"]
Supported Architectures, Distros and Languages
Currently, balenalib supports the following OS distributions and Language stacks, if you would like to see others added, create an issue on the balena base images repo.
|Distribution||Default (latest)||Supported Architectures|
|Debian||Debian GNU/Linux 10 (buster)||armv5e, armv6, armv7hf, aarch64, amd64, i386|
|Alpine||Alpine Linux v3.12||armv6, armv7hf, aarch64, amd64, i386|
|Ubuntu||18.04 LTS (bionic)||armv7hf, aarch64, amd64, i386|
|Fedora||Fedora 32||armv7hf, aarch64, amd64, i386|
|Language||Default (latest)||Supported Architectures|
|Node.js||15.2.1||armv6, armv7hf, aarch64, amd64, i386|
|Python||3.9.0||armv5e, armv6, armv7hf, aarch64, amd64, i386|
|OpenJDK||11-jdk||armv7hf, aarch64, amd64, i386, armv6|
|Go||1.15.3||armv7hf, aarch64, amd64, i386, armv6|
|Dotnet||3.1-sdk||armv7hf, aarch64, amd64|
Devices with a device type of
raspberry-pi (Raspberry Pi1 and Zero) will be built from
balenalib/rpi-raspbian and will be Raspbian base images. The
raspberrypi3 device types Debian base images have the Raspbian package source added, and Raspbian userland pre-installed.
Not all OS distro and language stack versions are compatible with each other. Notice that there are some combinations that are not available in the
balenalib base images.
- Node.js dropped 32-bit builds a while ago so i386-based nodejs images (Debian, Fedora and Ubuntu) v8.x and v6.x are official. New series (v10.x and v12.x) are using unofficial builds.
- armv6 binaries were officially dropped from Node.js v12 and v12 armv6 support is now considered unofficial.
- The Node.js v6.x and v8.x series are not available for i386 Alpine Linux base images v3.9 and edge as node crashes with segfault error, we are investigating the issue and will add them back as soon as the issue is resolved.
Installing software packages in balenalib containers is very easy, and in most cases, you can just use the base image operating system package manager. However to make things even easier, every balenalib image includes a small
install_packages script that abstracts away the specifics of the underlying package managers, and adds the following useful features:
- Install the named packages, skipping prompts etc.
- Clean up the package manager metadata afterward to keep the resulting image small.
- Retries if package install fails. Sometimes a package will fail to download due to a network issue, and retrying may fix this, which is particularly useful in an automated build pipeline.
An example of this in action is as follows:
FROM balenalib/raspberrypi3 RUN install_packages wget git CMD ["bash", "start.sh"]
This will run an
apt-get update -qq, then install
git via apt-get with
-y --no-install-recommends flags, and it will by default try this 2 times before failing. You can see the source of
How the Images Work at Runtime
On container startup, the entry.sh script first checks if the
UDEV flag is set to
false. In the case where it is
CMD is then executed. In the case it is
1), the entry.sh will check if the container is running privileged, if it is, it will mount
/dev to a devtmpfs and then start
udevd. In the case the container is an unprivileged container, no mount will be performed, and
udevd will be started (although it won't be very much use without the privilege).
At the end of a container's lifecycle, when a request to container restart, reboot or shutdown is sent to the supervisor, the balenaEngine will send a
SIGTERM (signal 15) to the containers, and 10 seconds later it will issue a
SIGKILL if the container is still running. This timeout can also be configured via the stop_grace_period in your docker-compose.yml.
Working with Dynamically Plugged Devices
In many IoT projects, your containers will want to interact with some hardware, often this hardware is plugged in at runtime, in the case of USB or serial devices. In these cases, you will want to enable
udevd in your container. In
balenalib images this can easily be done either by adding
ENV UDEV=1 in your
Dockerfile or by setting an environment variable.
You will also need to run your container
privileged. By default, any balenaCloud projects that don't contain a
docker-compose.yml will run their containers
privileged. If you are using a multicontainer project, you will need to add
privileged: true to each of the service definitions for the services that need hardware access.
balenalib container runs with
UDEV=1 it will first detect if it is running on a
privileged container. If it is, it will mount the host OS
/dev to a devtmpfs and then start
udevd. Now anytime a new device is plugged in, the kernel will notify the container
udevd daemon and the relevant device nodes in the container
/dev will appear.
Note: The new balenalib base images make sure
udevd runs in its own network namespace, so as to not interfere with cellular modems. These images should not have any of the past udev restrictions of the
resin/ base images.
When moving from the legacy
resin/... base images to the
balenalib ones, there are a number of breaking changes that you should take note of, namely:
UDEVnow defaults to
off, so if you have code that relies on detecting dynamically plugged devices, you will need to enable this in either your Dockerfile or via a device environment variable. See Working with Dynamically Plugged Devices.
INITSYSTEMfunctionality has been completely removed, so applications that rely on systemd or openRC should install and set up the initsystem in their apps. See Installing your own Initsystem.
- Mounting of
/devto a devtmpfs will now only occur when
UDEV=onand the container is running as
onare valid value for
UDEVand will be evaluated as
UDEV=on, all other values will turn
- Support for Debian Wheezy has been dropped.
armelarchitecture has been renamed to
Installing your own Initsystem
Since the release of multicontainer on the balenaCloud platform, we now recommend the use of multiple containers and no longer recommend the use of an initsystem, particularly systemd, in the container as it tends to cause a myriad of issues, undefined behavior and requires the container to run fully privileged.
However, if your application relies on initsystem features, it is fairly easy to add this functionality to a balenalib base image. We have provided some examples for systemd and openRC. Please note that different systemd versions require different implementation so for Debian Jessie and older, please refer to this example and for Debian Stretch and later, please refer to this example.
FROM balenalib/amd64-debian:buster # Install Systemd RUN apt-get update && apt-get install -y --no-install-recommends \ systemd \ systemd-sysv \ && rm -rf /var/lib/apt/lists/* ENV container docker # We never want these to run in a container # Feel free to edit the list but this is the one we used RUN systemctl mask \ dev-hugepages.mount \ sys-fs-fuse-connections.mount \ sys-kernel-config.mount \ display-manager.service \ getty@.service \ systemd-logind.service \ systemd-remount-fs.service \ getty.target \ graphical.target \ kmod-static-nodes.service COPY entry.sh /usr/bin/entry.sh COPY balena.service /etc/systemd/system/balena.service RUN systemctl enable /etc/systemd/system/balena.service STOPSIGNAL 37 ENTRYPOINT ["/usr/bin/entry.sh"] ################################## # Your code here... ##################################
Building ARM Containers on x86 Machines
This is a unique feature of balenalib ARM base images that allows you to run them anywhere (running ARM image on x86/x86_64 machines). A tool called
resin-xbuild and QEMU are installed inside any balenalib ARM base image and can be triggered by
RUN ["cross-build-start"] and
RUN ["cross-build-end"]. QEMU will emulate any instructions between
cross-build-end. So this Dockerfile:
FROM balenalib/armv7hf-debian RUN [ "cross-build-start" ] RUN apt-get update RUN apt-get install python-pip RUN pip install virtualenv RUN [ "cross-build-end" ]
can run on your x86 machine and there will be no
Exec format error, which is the error when you run an ARM binary on x86. This approach works only if the image is being built on x86 systems. Use the
--emulated flag in
balena push to trigger a qemu emulated build targetting the x86 architecture. More details can be found in our blog post here. You can find the full source code for the two cross-build scripts here.