From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: <isar-users@googlegroups.com>,
Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>
Subject: Re: [PATCH v5 3/5] classes: allow more control over container image name and tag
Date: Wed, 15 Dec 2021 17:17:31 +0100 [thread overview]
Message-ID: <20211215171731.7dfdd72e@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <afd32acd-ad8e-24e3-88a8-230e698f6c49@ilbers.de>
Am Wed, 18 Aug 2021 19:19:21 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:
> 05.08.2021 19:09, Henning Schild wrote:
> > diff --git a/doc/user_manual.md b/doc/user_manual.md
> > index cf7dc2fee35e..e5c07bd41fc5 100644
> > --- a/doc/user_manual.md
> > +++ b/doc/user_manual.md
> > @@ -1070,14 +1070,14 @@ bitbake -c do_populate_sdk
> > mc:qemuarm-buster:isar-image-base
> > - Load the SDK container image into the Docker Daemon
> >
> > ```
> > -docker load -i
> > build/tmp/deploy/images/qemuarm/sdk-debian-buster-armhf-docker-archive.tar.xz
> > +docker load -i
> > build/tmp/deploy/images/qemuarm/isar-image-base-debian-buster-armhf-1.0-r0-docker-archive.tar.xz
> > ```
> > - 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 +docker run --rm -ti --volume
> > "$(pwd):/build" isar-image-base-debian-buster-armhf:1.0-r0 ```
> >
> > - Check that cross toolchains are installed
> > diff --git a/meta/classes/image-sdk-extension.bbclass
> > b/meta/classes/image-sdk-extension.bbclass index
> > 426b92595554..fa15b588068c 100644 ---
> > a/meta/classes/image-sdk-extension.bbclass +++
> > b/meta/classes/image-sdk-extension.bbclass @@ -80,7 +80,7 @@
> > do_populate_sdk() { # generate the SDK in all the desired container
> > formats if [ -n "${sdk_container_formats}" ] ; then
> > bbnote "Generating SDK container in
> > ${sdk_container_formats} format"
> > - containerize_rootfs "${SDKCHROOT_DIR}"
> > "sdk-${DISTRO}-${DISTRO_ARCH}" "${sdk_container_formats}"
> > + containerize_rootfs "${SDKCHROOT_DIR}"
> > "${sdk_container_formats}" fi
> > }
> >
>
> This might be wrong. Containerized rootfs image and containerized sdk
> image are using the same name, so output files will be overwritten.
I will add a way to provide a prefix. So if one recipe needs to
generate multiple containers, sdk maybe just being one weird reason to
have multiple rootfs coming out of the same recipe.
That will allow this series to continue even whith the whole "SDK
should be an image" story still going on.
Henning
> Meantime normal non-containerized SDK image is still using
> sdk-*.tar.xz output file mask.
next prev parent reply other threads:[~2021-12-15 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 16:09 [PATCH v5 0/5] Allow better control over container tags Henning Schild
2021-08-05 16:09 ` [PATCH v5 1/5] classes: make sure container extension can run multiple times Henning Schild
2021-08-05 16:09 ` [PATCH v5 2/5] classes: simplify tag handling in container class Henning Schild
2021-08-05 16:09 ` [PATCH v5 3/5] classes: allow more control over container image name and tag Henning Schild
2021-08-18 16:19 ` Anton Mikanovich
2021-08-18 16:22 ` Jan Kiszka
2021-12-14 21:11 ` Henning Schild
2021-12-15 6:49 ` Schmidt, Adriaan
2021-12-15 16:17 ` Henning Schild [this message]
2021-08-05 16:09 ` [PATCH v5 4/5] classes: rename CONTAINER_FORMATS to CONTAINER_IMAGE_FORMATS Henning Schild
2021-08-05 16:09 ` [PATCH v5 5/5] classes: fix comment in container-img class Henning Schild
2021-08-05 16:12 ` [PATCH v5 0/5] Allow better control over container tags 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=20211215171731.7dfdd72e@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=amikan@ilbers.de \
--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