From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6916819860201668608 X-Received: by 2002:aa7:dc0d:: with SMTP id b13mr3105406edu.170.1610451624115; Tue, 12 Jan 2021 03:40:24 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a50:fd15:: with SMTP id i21ls3093722eds.1.gmail; Tue, 12 Jan 2021 03:40:23 -0800 (PST) X-Google-Smtp-Source: ABdhPJwZDvYKNiB3NvEQJQeJBBkVJQwjS4wt7yJUt8wViZ9+wHDsI5zdu4Z621yfKiRlKMCoExRP X-Received: by 2002:aa7:c358:: with SMTP id j24mr3073000edr.265.1610451623137; Tue, 12 Jan 2021 03:40:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610451623; cv=none; d=google.com; s=arc-20160816; b=b97Cg7+s8jQatVB1BNbX+1zN4LPyW/Ks8iKe3hWe7I7TyLLFEuYYF6oXX5CzQtfuzq 3Ucsjl3fnHtIegbgY3N2prESB2sQiPnCGzp127Pa0/TAg6YEcEVhd0CYzNxHwfDLMShj gMa4Tbt83aaLTRZGWLXNlIKtqJDDOzQLgRMmNrup+IlkRKkpXd/NcVCTC8mnQcqMMy7f QyPEcUgbGn9Js4gzNsIOuM1Ey/Flu5i7VUzO1PoTINDTtgQc8CsvGyD87za0m3+/uHLn W3MT03trHbOohM48QraY0OeKdzSiyygwkA41L+8Y9y+genzhOyxNtoDHhPs2NExJTaJb kfVg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=u7Xvhat3JW5p8NrK0lvy3Tpe7gkXyVvZU4PqxQTB6YM=; b=VgunWoCKW/lmOIt8f/eLWKO6Jb4y+OB2bA0dHskTBpeZVIJPib0BMO16z0pKtyJpjE rNzYB80eAqqlvIy55zgz+Ga4ffUMxZIN+I2tnvi21OTxvUqeoKfzKmtnG40bzjaXiy1q RO62IZrqJAMjX4mL1gsZK7BpEvqYPkCUMKTSbfQv25Aob/rhDnzO5ANpw8Usy49H23L6 FuutKMPCRjdtTk//aEevR1MYV5cJgwJ/21PWxLHvBUY8f9yQOHgac+CXK0Btj7x41ktz as9VjIcXFJY5861do/h8NbSshMz2Fv3v/kjsM+baSZDE4C/c3rmLSvJP9A5QEJvjASfN WjYA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id i3si125873edy.3.2021.01.12.03.40.23 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Jan 2021 03:40:23 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id 10CBeM2N017173 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 12 Jan 2021 12:40:22 +0100 Received: from md1za8fc.ad001.siemens.net ([139.22.47.251]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id 10CBeMih024479; Tue, 12 Jan 2021 12:40:22 +0100 Date: Tue, 12 Jan 2021 12:40:21 +0100 From: Henning Schild To: "[ext] Silvano Cirujano Cuesta" Cc: isar-users@googlegroups.com Subject: Re: [RFC PATCH 2/2] docs: document usage of sdk container images Message-ID: <20210112124021.5a9f44ce@md1za8fc.ad001.siemens.net> In-Reply-To: <20210112103338.14712-3-silvano.cirujano-cuesta@siemens.com> References: <20210112103338.14712-1-silvano.cirujano-cuesta@siemens.com> <20210112103338.14712-3-silvano.cirujano-cuesta@siemens.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: wWoR7/bYh24P Am Tue, 12 Jan 2021 11:33:38 +0100 schrieb "[ext] Silvano Cirujano Cuesta" : > Signed-off-by: Silvano Cirujano Cuesta > --- > doc/user_manual.md | 70 > ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 70 > insertions(+) > > diff --git a/doc/user_manual.md b/doc/user_manual.md > index a4f3d1d..ff779b1 100644 > --- a/doc/user_manual.md > +++ b/doc/user_manual.md > @@ -834,6 +834,76 @@ ii crossbuild-essential-armhf 12.3 > all Inf ~# > ``` > > +## Create a "containerized" ISAR SDK root filesystem > + > +### Motivation > + > +Distributing and using the SDK root filesystem created following the > instructions in "[Create an ISAR SDK root > filesystem](#create-an-isar-sdk-root-filesystem)" becomes easier > using container images (at least for those using containers anyway) > +A "containerized" SDK adds to those advantages of a normal SDK root > filesystem the comfort of container images. + +### Approach + +Create > container image with SDK root filesystem with installed > cross-toolchain for target architecture and ability to install > already prebuilt target binary artifacts. +Developer: > + - runs a container based on the resulting container image mounting > the source code to be built, > + - develops applications for target platform on the container and > + - leaves the container getting the results on the mounted directory. > + > +### Solution > + > +User specifies the variable `SDK_FORMAT` providing a space-separated > list of SDK formats to generate. +Supported formats are: > + - `tar`: is the default, is the non-containerized format that > results from following the instructions in "[Create an ISAR SDK root > filesystem](#create-an-isar-sdk-root-filesystem)" > + - `docker-archive`: an archive containing a Docker image that can > be imported with [`docker > import`](https://docs.docker.com/engine/reference/commandline/import/) > + - `docker-daemon`: (not supported from inside of a container) > resulting container image is made available on the local Docker Daemon > + - `containers-storage`: (not supported from inside of a container) > resulting container image is made available to tools using > containers/storage back-end (e.g. Podman, CRIO, buildah,...) > + - `oci-archive`: an archive containing an OCI image, mostly for > archiving as seed for any of the above formats + Maybe a script to postprocess the one tarball we have would be a better option. I do not understand why skopeo can not be used inside docker or podman, but we _really_ should not motivate anyone to run isar plain. Otherwise i agree that a bitbake task is a good idea and much better than postprocessing outside of the build system. Henning > +User manually triggers creation of SDK formats for his target > platform by launching the task `do_populate_sdk` for target image, > f.e. +`bitbake -c do_populate_sdk > mc:${MACHINE}-${DISTRO}:isar-image-base`. +Packages that should be > additionally installed into the SDK can be appended to > `SDK_PREINSTALL` (external repositories) and `SDK_INSTALL` > (self-built). + +The resulting SDK formats are archived into > `tmp/deploy/images/${MACHINE}/sdk-${DISTRO}-${DISTRO_ARCH}-${sdk_format}.tar.xz` > (being `sdk_format` each one of the formats specified in > `SDK_FORMATS`). +The SDK container directory `/isar-apt` contains a > copy of isar-apt repo with locally prebuilt target debian packages > (for ). +One may get into an SDK container and install > required target packages with the help of `apt-get install > :` command. +The directory with the source > code to develop on should be mounted on the container (with `--volume > :`) to be able to edit files in > the host with an IDE and build in the container. + +### Example + > + - Make the SDK formats to generate available to the task > + > +For one-shot builds (use `local.conf` otherwise): > + > +``` > +export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE SDK_FORMATS" > +export SDK_FORMATS="docker-archive" > +``` > + > + - Trigger creation of SDK root filesystem > + > +``` > +bitbake -c do_populate_sdk mc:qemuarm-buster:isar-image-base > +``` > + > + - Load the SDK container image into the Docker Daemon > + > +``` > +xzcat > build/tmp/deploy/images/qemuarm/sdk-debian-buster-armhf-docker-archive.tar.xz > | docker load +``` + > + - Run a container using the SDK container image (following commands > starting with `#~:` are to be run in the container) + > +``` > +docker run --rm -ti --volume "$(pwd):/build" > isar-sdk-buster-armhf:latest +``` > + > + - Check that cross toolchains are installed > + > +``` > +:~# dpkg -l | grep crossbuild-essential-armhf > +ii crossbuild-essential-armhf 12.3 all > Informational list of cross-build-essential packages +``` > + > ## Creation of local apt repo caching upstream Debian packages > > ### Motivation