Re: [RFC PATCH 0/2] support generation of sdk container images

[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(-)
>