From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Silvano Cirujano Cuesta" <silvano.cirujano-cuesta@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [RFC PATCH 0/2] support generation of sdk container images
Date: Thu, 14 Jan 2021 19:32:37 +0100 [thread overview]
Message-ID: <20210114193237.28c8448b@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <b141eeb7-0f34-5cbd-bcea-437d8b914804@siemens.com>
Please do not make my voice count too much, the moment i see "docker" i
go "strong reject". A reflex i can not help ... maybe its valuable and
i am too much blinded by stereotypes.
Henning
Am Thu, 14 Jan 2021 14:56:59 +0100
schrieb "[ext] Silvano Cirujano Cuesta"
<silvano.cirujano-cuesta@siemens.com>:
> I wonder how to interpret the current feelings about this proposal:
>
> * There's no interest at all.
>
> * I haven't succeed on raising enough interest. In that case I'd
> need more input from people who see the demand for this functionality
> to better understand what's missing in my proposal.
>
> * There's interest, but I should update the patch according the
> comments up-to-now before I send a 1st patch series proposal (or a
> 2nd RFC).
>
> I'd appreciate any feedback. The more decision power the person
> giving the feedback, the more valuable it is for me :-)
>
> Thanks!
>
> Silvano
>
>
> On 12/01/2021 11:33, [ext] Silvano Cirujano Cuesta wrote:
> > This patch series adds to the SDK generation (task `populate_sdk`)
> > the possibility of generating container images containing the SDK in
> > different formats (multiple formats can be generated at once).
> >
> > Up-to-now the task `populate_sdk` generates the sdk root filesystem
> > (in both as a file tree and in a tarball) that can be chrooted to.
> > The same root filesystem can be easily distributed as a container
> > image and started as a container.
> >
> > It's even possible extracting the root filesystem from a container
> > image, using the container image format only as a sort of packaging
> > system for easy distribution.
> >
> > More information about its usage is documented in the file
> > docs/user_manual.md.
> >
> > 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.
> >
> > Silvano Cirujano Cuesta (2):
> > sdk: support creation of container image
> > docs: document usage of sdk container images
> >
> > doc/user_manual.md | 70 +++++++++++++++++
> > meta/classes/image-sdk-extension.bbclass | 99
> > ++++++++++++++++++++++-- 2 files changed, 162 insertions(+), 7
> > deletions(-)
>
next prev parent reply other threads:[~2021-01-14 18:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 10:33 Silvano Cirujano Cuesta
2021-01-12 10:33 ` [RFC PATCH 1/2] sdk: support creation of container image Silvano Cirujano Cuesta
2021-01-12 11:36 ` Henning Schild
2021-01-12 11:50 ` Silvano Cirujano Cuesta
2021-01-12 14:50 ` Jan Kiszka
2021-01-12 17:08 ` Silvano Cirujano Cuesta
2021-01-12 17:36 ` Henning Schild
2021-01-12 17:54 ` Silvano Cirujano Cuesta
2021-01-12 18:04 ` Jan Kiszka
2021-01-12 20:46 ` Silvano Cirujano Cuesta
2021-01-12 10:33 ` [RFC PATCH 2/2] docs: document usage of sdk container images Silvano Cirujano Cuesta
2021-01-12 11:40 ` Henning Schild
2021-01-12 12:03 ` Silvano Cirujano Cuesta
2021-01-12 12:18 ` Henning Schild
2021-01-12 14:52 ` Silvano Cirujano Cuesta
2021-01-12 14:56 ` Jan Kiszka
2021-01-12 15:12 ` Silvano Cirujano Cuesta
2021-01-12 15:14 ` Jan Kiszka
2021-01-12 15:11 ` Henning Schild
2021-01-12 16:26 ` Silvano Cirujano Cuesta
2021-01-14 13:56 ` [RFC PATCH 0/2] support generation " Silvano Cirujano Cuesta
2021-01-14 18:32 ` Henning Schild [this message]
2021-01-15 8:11 ` Silvano Cirujano Cuesta
2021-01-15 7:09 ` Jan Kiszka
2021-01-15 8:16 ` 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=20210114193237.28c8448b@md1za8fc.ad001.siemens.net \
--to=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