If you are using Dockerfile.template, you can replace with %%BALENA_MACHINE_NAME%% or %%BALENA_ARCH%%. is either architecture or device type and is mandatory.In general, the naming scheme for the balenalib image set follows the pattern below: balenalib/-:-(build|run)- Image Names To pick the correct image, it helps to understand how the images are named as that indicates what is installed in the image. With over 26000 balenalib base images to choose from, it can be overwhelming to decide which image and tag are correct for your project. 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. 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. 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. These images help you get setup faster and work out the requirements for your project. When starting out a project, it's generally easier to have a "fatter" image, which contains a lot of prebuilt dependencies and tools. Helpful package installer script called install_packages inspired by minideb.cross-build functionality for building ARM containers on x86.run and build variants designed for multistage builds.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |