Re: docker-image-debian-all-test-cross errors

["Alex Bennée" <alex.bennee@linaro.org>]

Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com> writes:

> On 7/6/2026 1:35 AM, Alex Bennée wrote:
>> Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> writes:
>> 
>>> On 05/07/2026 10:07, Michael Tokarev wrote:
>>>
>>>> On 05.07.2026 00:20, Richard Henderson wrote:
>>>>> Has anyone else been seeing
>>>>>
>>>>> Error: Failed to fetch
>>>>> http://deb.debian.org/debian/pool/main/d/dpkg/ libdpkg-
>>>>> perl_1.22.21_all.deb  404  Not Found [IP: 151.101.22.132 80]
>>>> ...
>>>> dpkg (and all related packages) has been upgraded from 1.22.21 to
>>>> 1.22.22 version quite a while (on Mar-2026).  Initially debian trixie
>>>> had dpkg 1.22.21.
>>>> I wonder where it is getting the old version reference from?
>>>> Should the previous layer be refreshed to point to the current trixie
>>>> point release?
>>>> /mjt
>>>
>>> If that is the case then I think you can fix it by doing a manual
>>> update of the base image to pull in the latest update locally i.e.
>>> "docker pull docker.io/library/debian:13-slim" and then rebuilding the
>>> docker images once again?
>> 
>> You can always trigger a local build:
>> 
>>   make docker-image-all-test-cross NOCACHE=1
>> 
>> it looks like the source tree build of images has been broken again as
>> UNCHECKED_GOALS isn't being honoured for me.
>> 
>>>
>>>
>>> ATB,
>>>
>>> Mark.
>> 
>
> The right fix is to modify our dockerfiles to always combine apt update
> and apt install, to avoid those kind of errors.

We do for the main part of the dependencies from lcitool. We then do a
second step for the cross compilers for which there are shenanigans to
deal with non-x86 arches before installing them.

But the original failure from perl should have been picked up by the
first bit.

>
> See this doc for more details:
> https://docs.docker.com/build/building/best-practices/#apt-get
>
> Regards,
> Pierrick

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro