[PATCH] docker: Use GitHub-mirrored TF-A repository to avoid clone failures
Jerome Forissier
jerome.forissier at linaro.org
Fri Nov 28 12:24:32 CET 2025
On 11/28/25 12:12, Peter Robinson wrote:
> On Mon, 10 Nov 2025 at 14:03, Bin Meng <bmeng.cn at gmail.com> 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 \
>
> If you're going to use a github mirror use the TFA one, I've seen
> issues with the way they sync to the one above in the past where
> things like tags disappear.
>
> https://github.com/TrustedFirmware-A/trusted-firmware-a/
+1, good catch. It's then one we've been using for OP-TEE CI.
Thanks,
--
Jerome
>
>> -b v2.13.0 && \
>> cd /tmp/tf-a/ && \
>> make CROSS_COMPILE=/opt/gcc-${TCVER}-nolibc/aarch64-linux/bin/aarch64-linux- \
>> --
>> 2.34.1
>>
More information about the U-Boot
mailing list