26a7ab8f48
Container engines per default log all container output into journald (Podman) or a json file (Docker). A build with kas-container/bitbake containes lots of useless build output like progress lines, etc. In case of Podman, where journald is used, this means that all this is spammed into the journald buffer and possible also send to ttys or even serial ttys. This might make sense for containers that output only status information about running services, but for a build process, this is mostly just spamming and causes important information to be lost. Since the stdout/stderr output of the container is used for kas-container ordinarily, the background logging from the container image can be deactivated. Therefor add the `--log-driver=none` parameter to all container runtimes command lines. Signed-off-by: Claudius Heine <ch@denx.de> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Setup tool for bitbake based projects ===================================== +--------------------+ | Build Status | +====================+ | |workflow-master|_ | +--------------------+ | |workflow-next|_ | +--------------------+ .. |workflow-master| image:: https://github.com/siemens/kas/workflows/master/badge.svg .. _workflow-master: https://github.com/siemens/kas/actions?query=workflow%3Amaster .. |workflow-next| image:: https://github.com/siemens/kas/workflows/next/badge.svg .. _workflow-next: https://github.com/siemens/kas/actions?query=workflow%3Anext This tool provides an easy mechanism to setup bitbake based projects. The OpenEmbedded tooling support starts at step 2 with bitbake. The downloading of sources and then configuration has to be done by hand. Usually, this is explained in a README. Instead kas is using a project configuration file and does the download and configuration phase. Key features provided by the build tool: - clone and checkout bitbake layers - create default bitbake settings (machine, arch, ...) - launch minimal build environment, reducing risk of host contamination - initiate bitbake build process See the `kas documentation <https://kas.readthedocs.io>`_ for further details.