[Help needed] containers with unready status timeout

Context

I'm making runners for a gitlab pipelines for Unity I'm adding them to my VPS with a kubernetes

However when i'm trying to run i've got this issue : https://pastecord.com/ugebocyhak.sql

It's strange because when i delete and re-add the gitlab runner instance with helm, i've got the thing running, but at some point, it start to get the error.

My theories :

Image too long to pull

Its a fact, the image is big, however i don't think it should be an issue because i think (i hope) they programmed it correctly so if its currently pulling the image, it should wait without having a timeout....

When i tried to build using my organisation's runners (it runs directly on the servers, its not using kubernetes), i could have all the time i wanted to pull the image, it was inside the job's process, it did not have a timeout like that, aswell as no waiting for pod

Here is the thing that makes me think that : https://pastecord.com/ybisetinag.properties Logs : https://pastecord.com/ijopagugac.kt

Not enougth space

While i still have 22 GB of space avaliable (34%), because an image is big, and builds are big, i think i've got the issue because it could take all of the space avaliable ?

Kubectl df of the gitlab runner holder : https://pastecord.com/popugesoka.yaml