kas container contains too many dev packages

[Ross Burton]

Hi,

We just had to hunt down a build failure which only occured on some developers machines because many machines - and the Kas container - have uuid-dev installed which was masking a native build dependency.

Indeed, this was unexpected inside the latest kas container:

$ dpkg -l \*-dev |grep ^ii|wc -l
62

I see uuid-dev but also the X11 and Mesa stacks.  Is there a reason there's a lot of -dev packages installed into the build container?

Cheers,

Ross

[Jan Kiszka]

I suspect it is primarily coming from [1]. We didn't check this list in
a while against latest Yocto demands, maybe it become too large?

But maybe there is also a chance to split between a set needed for full
from-source builds vs. buildtools-based compilations. Conceptually,
there should be...

Jan

[1]
https://github.com/siemens/kas/blob/08047b320d0a6c0291e948966e8fc41ea45aabf5/Dockerfile#L136

--
Siemens AG, Foundational Technologies
Linux Expert Center

[Jan Kiszka]

On 21.05.26 07:35, 'Jan Kiszka' via kas-devel wrote:
> On 20.05.26 14:49, Ross Burton wrote:
>> Hi,
>>
>> We just had to hunt down a build failure which only occured on some
>> developers machines because many machines - and the Kas container -
>> have uuid-dev installed which was masking a native build dependency.
>>
>> Indeed, this was unexpected inside the latest kas container:
>>
>> $ dpkg -l \*-dev |grep ^ii|wc -l
>> 62
>>
>> I see uuid-dev but also the X11 and Mesa stacks.  Is there a reason
>> there's a lot of -dev packages installed into the build container?
>>
>
> I suspect it is primarily coming from [1]. We didn't check this list in
> a while against latest Yocto demands, maybe it become too large?
>
> But maybe there is also a chance to split between a set needed for full
> from-source builds vs. buildtools-based compilations. Conceptually,
> there should be...
>

I just did a quick diff between kas Dockerfile and Yocto 6.0 needs [1]:

- kas is missing formally (but all packages pulled otherwise):
- file
- libacl1
- libcrypt-dev
- locales

- kas is shipping too much:
- libegl1
- libsdl1.2-dev
- pylint
- xterm
- mesa-common-dev
- lz4

Going back to Yocto 3.0, e.g., these packages used to be required. I
just dropped those, and we would be down to about 946MB image size.

Now the tricky question obviously is: what is the oldest Yocto version
people may still build with a recent kas image? It is likely not 3.0...
If you can figure out a reasonable limit and derive an updated
dependency list from that, we can likely clean up here.

Jan

[1]
https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html#build-host-packages
[2]
https://docs.yoctoproject.org/3.0/ref-manual/ref-manual.html#ubuntu-packages

[Ross Burton]

On Thu, 21 May 2026 at 15:26, 'Jan Kiszka' via kas-devel <kas-...@googlegroups.com> wrote:

Going back to Yocto 3.0, e.g., these packages used to be required. I
just dropped those, and we would be down to about 946MB image size.

Now the tricky question obviously is: what is the oldest Yocto version
people may still build with a recent kas image? It is likely not 3.0...
If you can figure out a reasonable limit and derive an updated
dependency list from that, we can likely clean up here.

Well according to https://www.yoctoproject.org/development/releases/ 5.0 is the latest supported release as kirkstone (4.0) went EOL last month.  You could be really generous and support kirkstone for a bit more time.

Ross 

[Jan Kiszka]

Right, but then we need to keep xterm & Co. for now. Only 5.0 seems to
have shrunken the list.

Jan