Re: Assistance Requested: GitLab CI build Failure During Docker Image Pull (unexpected EOF)

[vitaly prosyak <vprosyak@amd.com>]

Hi Kamil,

Thank you very much for the clarification and for re-running the pipeline — I really appreciate you taking the time to look into it and confirm it was just a transient network issue.

That makes perfect sense. It’s good to know that these kinds of Docker pull failures can occasionally happen and usually resolve after a re-run. I’m glad everything looks fine now.

Thanks as well for explaining that there isn’t much to do from my side in such cases. I’ll keep that in mind and won’t worry if I see a similar failure again unless it’s a real build or test issue.

And thank you for the note about IRC — I’ll keep #igt on OFTC in mind if something urgent comes up. Of course, I completely understand there can be delays, especially around holidays.

Really appreciate your help and support.

Best regards,
Vitaly


On 2026-02-23 07:36, Kamil Konieczny wrote:
> Hi Vitaly,
> On 2026-02-21 at 23:43:08 -0500, vitaly prosyak wrote:
>> Hi Kamil,
>>
>> I hope you’re doing well.
>>
>> I noticed a GitLab CI failure(https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/jobs/93765548) 
>>
>>  after the recent IGT patches were merged, but it looks unrelated to the code changes—the job fails before any build or test steps start.
>>
>> The failure happens while pulling the Docker image:
>>
>> registry.freedesktop.org/drm/igt-gpu-tools/build-debian
>>
>> The runner reports:
>> “failed to pull image … writing blob … storing blob to file under /var/tmp … happened during read: unexpected EOF”
>>
>> This seems consistent with an interrupted image download (e.g., transient network/registry issue) or a runner-side storage/tmp problem (since it fails while writing into /var/tmp).
>>
>> If you have a moment, could you please take a look on the runner side—especially:
>>
>>   *
>>
>>     available disk space (including /var/tmp),
>>
>>   *
>>
>>     whether there may be a corrupted cached image layer,
>>
>>   *
>>
>>     and whether a cache cleanup / forced re-pull would help?
>>
> That was network problem, for example broken or slow connection.
> I happens sometimes and could go away at next merged changes or
> when admin (for example me) re-run failed pipelines. I did it
> today and seems all is ok now.
>
>> Also, please let me know if there’s anything I can do from my side to help (e.g., provide the full job log link/details, re-run specific jobs, or test a workaround).
>>
> I do not know of any other way besides re-run. The only problem
> where you could help would be when an actual compilation bug would
> happen.
>
> Btw you could also ping me on irc oftc #igt channel. Please expect
> few hours/days/sometimes weeks delay, especially when on holidays.
>
>> Thank you very much for your help.
>>
>> Best regards,
>> Vitaly
>>
> +cc other admins, Karthik, J-P and Ashutosh
> Cc: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> Cc: Juha-Pekka Heikkila <juha-pekka.heikkila@intel.com>
> Cc: Karthik B S <karthik.b.s@intel.com>
> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
>
> Regards,
> Kamil