From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Cc: Schaffner@shymkent.ilbers.de, Tobias <tobias.schaffner@siemens.com>
Subject: Re: [PATCH 1/3] testsuite: Dockerfile for isar-docker image
Date: Thu, 9 Mar 2023 10:05:02 +0100 [thread overview]
Message-ID: <ZAmhPrYxxVpCOPzC@ilbers.de> (raw)
In-Reply-To: <978dd08a-bff6-eefa-1b54-8388ecbcf56c@siemens.com>
Thanks Tobias for the quick review,
On 2023-03-09 07:57, Schaffner, Tobias wrote:
> Why not choose kas-isar as parent image and just add the CI specific
> needs? Is there a reason why you want to maintain this a second time?
Our preferred way would actually be to fix specific versions of avocado and (if
necessary) qemu in the kas-isar image and continue using it. The new image was
created with the minimal Isar requirements (kas-isar has some 300 MB of
additional packages). We'll check kas-isar as parent and let you know. We'll
probably need some sync on it, like user ID handling, which image version will
be used when, planned updates, etc.
With kind regards,
Baurzhan
next prev parent reply other threads:[~2023-03-09 9:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 4:36 [PATCH 0/3] Switch to own " Uladzimir Bely
2023-03-07 4:36 ` [PATCH 1/3] testsuite: Dockerfile for " Uladzimir Bely
2023-03-09 7:57 ` Schaffner, Tobias
2023-03-09 9:05 ` Baurzhan Ismagulov [this message]
2023-03-09 9:14 ` Uladzimir Bely
2023-03-09 11:10 ` Jan Kiszka
2023-03-09 11:07 ` Jan Kiszka
2023-03-07 4:36 ` [PATCH 2/3] testsuite: Add README for isar-docker Uladzimir Bely
2023-03-07 4:36 ` [PATCH 3/3] gitlab-ci: Switch to own isar-docker image Uladzimir Bely
2023-03-14 13:49 ` [PATCH 0/3] " Henning Schild
2023-03-14 14:00 ` Jan Kiszka
2023-03-14 14:25 ` Henning Schild
2023-03-14 14:28 ` Jan Kiszka
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=ZAmhPrYxxVpCOPzC@ilbers.de \
--to=ibr@radix50.net \
--cc=Schaffner@shymkent.ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=tobias.schaffner@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