Re: [PATCH 1/3] testsuite: Dockerfile for isar-docker image

[Jan Kiszka <jan.kiszka@siemens.com>]

On 09.03.23 10:14, Uladzimir Bely wrote:
> In the email from Thursday, 9 March 2023 12:05:02 +03 user Baurzhan Ismagulov wrote:
>> 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
>>wise
>>
> 
> Yes, the only reason was just to have the image size as small as possible, but enough to build Isar. Our own image with avocado and qemu inside got size of 1.07GB. It's a bit less than 1.29GB we get in case of basing on kas-isar (823MB) with additional testsuite stuff.
> If size does not matter, it would be even better and easier for us to base on kas-isar, with similar version tagging scheme.

kas-isar is the minimal image needed for building Isar, that's its
purpose. You can read that up in the image description, and we maintain
that description in lock-step with Isar's documentation (at least that
is the goal).

Again, trying to roll your own for testing purposes only will not be
beneficial for the ecosystem.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux