From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Silvano Cirujano Cuesta"
<silvano.cirujano-cuesta@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v5 0/4] Add support for containerized root filesystems
Date: Tue, 23 Feb 2021 09:03:43 +0100 [thread overview]
Message-ID: <2d13129d-953d-6bca-cbd7-f1f6e19337d5@siemens.com> (raw)
In-Reply-To: <20210215133918.50988-1-silvano.cirujano-cuesta@siemens.com>
On 15.02.21 14:39, [ext] Silvano Cirujano Cuesta wrote:
> This patch series provides support for containerized root filesystems,
> for both target images and SDKs.
>
> For containerized target images the new image type `container-img` has
> been added.
>
> For containerized SDKs the task `populate_sdk` has been extended.
>
> Containerized root filesystems are easy to distribute and run, enabling
> this way following scenarios:
> - Use ISAR to build container images meant to be run only in containers.
> - Use the same ISAR configuration to build images for containers, VMs
> and bare-metal.
> - Easy SDK distribution and "installation".
> - Quickly testing certain applications in the workstation using the
> target root filesystem.
>
> In order to build containerized target root filesystems `IMAGE_TYPE` has
> to be `container-img`, additionally the container image format can be
> selected with the variable `CONTAINER_FORMATS`. The default format is
> `docker-archive`.
>
> In order to build containerized SDKs the variable `SDK_FORMAT` has to
> provide any of the supported container formats (e.g. `docker-archive`).
> The default format is the legacy non-containerized: `tar_xz`.
>
> More information about its usage is documented in the file
> docs/user_manual.md.
>
> A PoC/demo of this functionality (only the SDK part) has been created
> based on the project https://github.com/siemens/meta-iot2050.
> Jan Kiszka already tested and liked it! =>
> https://github.com/siemens/meta-iot2050/issues/86#issuecomment-768907845
>
> Successful builds of both containerized target and SDK are available on
> the same PoC project:
> - https://github.com/Silvanoc/meta-iot2050/actions/runs/558311580
> - https://github.com/Silvanoc/meta-iot2050/actions/runs/558311581
> and also the resulting images:
> - https://github.com/users/Silvanoc/packages/container/package/meta-iot2050%2Fiot2050-debian-arm64
> - https://github.com/users/Silvanoc/packages/container/package/meta-iot2050%2Fiot2050-debian-sdk-arm64
>
> In order to get a feeling about its usage (you need Docker or Podman),
> follow these simple copy&paste instructions:
> https://github.com/Silvanoc/meta-iot2050/blob/master/kas/BUILDING-SDK-CONTAINER.md#running-the-sdk
> Build instructions are available in the upper part of that document.
>
> Two new dependencies are required to create containerized root
> filesystems (as specified in the documentation).
>
> Typical container image management actions (e.g. push an image to a
> container image regitry) are out of scope. Available tools (Docker,
> Skopeo, Buildah, Podman,...) should be used for these actions.
>
> A patch will follow this one to get the dependencies into the container
> images being provided by the project
> https://github.com/siemens/kas (for `kas-container`, for example).
>
> Silvano Cirujano Cuesta (4):
> classes: add root filesystem containerizing class
> classes: add new image type 'container-img'
> sdk: add support for containerized sdk
> docs: document creation of container images
>
> doc/user_manual.md | 127 ++++++++++++++++++
> meta/classes/container-img.bbclass | 18 +++
> .../classes/image-container-extension.bbclass | 79 +++++++++++
> meta/classes/image-sdk-extension.bbclass | 42 +++++-
> meta/classes/image.bbclass | 1 +
> 5 files changed, 260 insertions(+), 7 deletions(-)
> create mode 100644 meta/classes/container-img.bbclass
> create mode 100644 meta/classes/image-container-extension.bbclass
>
Looks good to me.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-02-23 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 13:39 Silvano Cirujano Cuesta
2021-02-15 13:39 ` [PATCH v5 1/4] classes: add root filesystem containerizing class Silvano Cirujano Cuesta
2021-02-15 13:39 ` [PATCH v5 2/4] classes: add new image type 'container-img' Silvano Cirujano Cuesta
2021-02-15 13:39 ` [PATCH v5 3/4] sdk: add support for containerized sdk Silvano Cirujano Cuesta
2021-02-15 13:39 ` [PATCH v5 4/4] docs: document creation of container images Silvano Cirujano Cuesta
2021-02-22 9:16 ` [PATCH v5 0/4] Add support for containerized root filesystems Silvano Cirujano Cuesta
2021-02-23 8:03 ` Jan Kiszka [this message]
2021-03-02 9:05 ` Anton Mikanovich
2021-03-02 9:30 ` Silvano Cirujano Cuesta
2021-03-02 13:30 ` Anton Mikanovich
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=2d13129d-953d-6bca-cbd7-f1f6e19337d5@siemens.com \
--to=jan.kiszka@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