1682eb1f44
Added docker_extern_containers bbclass that installs external docker images that have been exported. The import-docker-image recipe has been renamed to import-docker-containers and updated to install a new init script that imports all of the docker containers when the image boots. The new init script now attempts to start the docker daemon if it is not already running. Issue-Id: SCM-1811 Signed-off-by: Nathan Dunne <Nathan.Dunne@arm.com> Change-Id: Icd8222775ca9f640856a4ad4b51b18de17e5680d Signed-off-by: Jon Mason <jon.mason@arm.com>
Introduction
This repository contains Arm layers for OpenEmbedded
meta-arm: This layer provides support for general recipes for the Arm architecture. Anything that's not needed explicitly for BSPs, the IOTA distribution, or destined to be upstreamed belongs here.
meta-arm-bsp: This layer provides support for Arm reference platforms
meta-arm-iota: This layer provides support for Arm's IOTA Linux Distribution
meta-arm-toolchain: This layer provides support for Arm's GNU-A toolset releases
meta-arm-autonomy: This layer provides a reference stack for autonomous systems.
Contributing
Currently, we only accept patches from the meta-arm mailing list. For general information on how to submit a patch, please read https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
E-mail meta-arm@lists.yoctoproject.org with patches created using this process. You can configure git-send-email to automatically use this address for the meta-arm repository with the following git command:
$ git config --local --add sendemail.to meta-arm@lists.yoctoproject.org
Commits and patches added should follow the OpenEmbedded patch guidelines:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
The component being changed in the shortlog should be prefixed with the layer name (without the meta- prefix), for example:
arm-bsp/trusted-firmware-a: decrease frobbing level
arm-toolchain/gcc: enable foobar v2
Reporting bugs
E-mail meta-arm@lists.yoctoproject.org with the error encountered and the steps to reproduce the issue.
Maintainer(s)
- Jon Mason jon.mason@arm.com
- Ross Burton ross.burton@arm.com