public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Bezdeka, Florian" <florian.bezdeka@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Cirujano Cuesta, Silvano" <silvano.cirujano-cuesta@siemens.com>
Cc: "felix.moeser@siemens.com" <felix.moeser@siemens.com>,
	"henning.schild@siemens.com" <henning.schild@siemens.com>
Subject: Re: [PATCH v8 1/5] classes: add root filesystem containerizing class
Date: Fri, 20 Aug 2021 08:54:19 +0200	[thread overview]
Message-ID: <20275c19-3598-b750-4035-8267ecbc3995@siemens.com> (raw)
In-Reply-To: <37a688793ec39c0dc34a95c452d1dc2c0920d6b4.camel@siemens.com>

On 19.08.21 22:43, Bezdeka, Florian wrote:
> On Mon, 2021-03-29 at 17:56 +0200, [ext] Silvano Cirujano Cuesta wrote:
>> This class can be used to create container images which root filesystem
>> is that generated by the do_rootfs task.
>>
>> Containerized root filesystems have following possible use-cases:
>>  - Using ISAR as a container image builder.
>>  - Simplify distribution of runtime rootfs (binaries, libraries,
>>    configurations, ...) for application development or testing.
>>  - Distributing SDKs.
>>
>> Signed-off-by: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>
>> ---
>>  .../classes/image-container-extension.bbclass | 82 +++++++++++++++++++
>>  meta/classes/image.bbclass                    |  1 +
>>  2 files changed, 83 insertions(+)
>>  create mode 100644 meta/classes/image-container-extension.bbclass
>>
>> diff --git a/meta/classes/image-container-extension.bbclass b/meta/classes/image-container-extension.bbclass
>> new file mode 100644
>> index 0000000..f693627
>> --- /dev/null
>> +++ b/meta/classes/image-container-extension.bbclass
>> @@ -0,0 +1,82 @@
>> +# This software is a part of ISAR.
>> +# Copyright (C) Siemens AG, 2021
>> +#
>> +# SPDX-License-Identifier: MIT
>> +#
>> +# This class extends the image.bbclass for containerizing the root filesystem.
>> +
>> +CONTAINER_FORMATS ?= "docker-archive"
>> +IMAGE_INSTALL += "isar-exclude-docs isar-disable-apt-cache"
>> +
>> +containerize_rootfs() {
>> +    local cmd="/bin/dash"
>> +    local empty_tag="empty"
>> +    local full_tag="latest"
>> +    local oci_img_dir="${WORKDIR}/oci-image"
>> +    local rootfs="$1"
>> +    local rootfs_id="$2"
>> +    local container_formats="$3"
>> +
>> +    # prepare OCI container image skeleton
>> +    bbdebug 1 "prepare OCI container image skeleton"
>> +    rm -rf "${oci_img_dir}"
>> +    sudo umoci init --layout "${oci_img_dir}"
> 
> Sorry for replying to this quite old thread but the timestamp of the
> commit actually delivered this patch as root cause:
> 
> Who makes sure umoci is available?
> 

The build environment you need to prepare for Isar, either a manually
installed Debian or a container like kas-isar.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

  reply	other threads:[~2021-08-20  6:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 15:56 [PATCH v8 0/5] Add support for containerized root filesystems Silvano Cirujano Cuesta
2021-03-29 15:56 ` [PATCH v8 1/5] classes: add root filesystem containerizing class Silvano Cirujano Cuesta
2021-04-08 17:55   ` Jan Kiszka
2021-04-12  7:14     ` Silvano Cirujano Cuesta
2021-04-12  8:20     ` Silvano Cirujano Cuesta
2021-08-19 20:43   ` Bezdeka, Florian
2021-08-20  6:54     ` Jan Kiszka [this message]
2021-08-31 12:56       ` Silvano Cirujano Cuesta
2021-03-29 15:56 ` [PATCH v8 2/5] classes: add new image type 'container-img' Silvano Cirujano Cuesta
2021-03-29 15:56 ` [PATCH v8 3/5] sdk: add support for containerized sdk Silvano Cirujano Cuesta
2021-03-29 15:56 ` [PATCH v8 4/5] docs: document creation of container images Silvano Cirujano Cuesta
2021-03-29 15:56 ` [PATCH v8 5/5] ci: add container image sample configurations Silvano Cirujano Cuesta
2021-04-02 15:18 ` [PATCH v8 0/5] Add support for containerized root filesystems Anton Mikanovich
2021-04-06  5:23   ` Silvano Cirujano Cuesta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20275c19-3598-b750-4035-8267ecbc3995@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=felix.moeser@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=silvano.cirujano-cuesta@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox