[PATCH] docker: Use GitHub-mirrored TF-A repository to avoid clone failures

[Jerome Forissier]

On 11/26/25 16:41, Tom Rini wrote:
> On Mon, Nov 10, 2025 at 09:37:58PM +0800, Bin Meng wrote:
> 
>> GitHub Actions consistently fails to clone the upstream TF-A repo,
>> returning the error: "The requested URL returned error: 403".
>>
>> To improve compatibility in building the docker image with GitHub
>> Actions, switch to the GitHub-mirrored TF-A repository instead.
>>
>> Signed-off-by: Bin Meng <bmeng.cn at gmail.com>
>> ---
>>
>>  tools/docker/Dockerfile | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile
>> index d2384219c06..201a1cdbac1 100644
>> --- a/tools/docker/Dockerfile
>> +++ b/tools/docker/Dockerfile
>> @@ -243,7 +243,7 @@ RUN git clone --depth=1 https://github.com/OP-TEE/optee_os.git /tmp/optee_os \
>>  
>>  # Build fiptool, bl1 and fip for fvp and qemu_arm64
>>  RUN git clone --depth=1 -b mbedtls-3.6 https://github.com/ARMmbed/mbedtls.git /tmp/mbedtls
>> -RUN git clone --depth=1 https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git /tmp/tf-a \
>> +RUN git clone --depth=1 https://github.com/ARM-software/arm-trusted-firmware.git /tmp/tf-a \
>>  	-b v2.13.0 && \
>>  	cd /tmp/tf-a/ && \
>>  	make CROSS_COMPILE=/opt/gcc-${TCVER}-nolibc/aarch64-linux/bin/aarch64-linux- \
> 
> How consistent is this failure? I've had problems this past year
> building various parts of the container due to AI scraper overloads but
> never had a problem with the TF-A repository.

FWIW,

The OP-TEE OS CI is also running GitHub Actions, and I have seen Git clone
failures with projects hosted on git.trustedfirmware.org on several occasions
(TF-A, Hafnium). GitHub on the other hand has been rock solid and fast (not
surprising I suppose, since this is GitHub <-> GitHub).

-- 
Jerome