I have two ideas to solve the issue:
A. Put the file on company owned s3 bucket.
B. Store binary file on the host-os and mount it in after the startup of the vm. This would make the default setup of the Cilicon, more stable.
Do we have any idea of how to start implementing option B?
I suppose this is the issue for all the runners and not explicit gitlab.
I can try to implement it but currently don't know where to start, unless I go with option A.
After each Cilicon cycle the gitlab-runner is downloaded from the internet. When downloading from default location: https://gitlab-runner-downloads.s3.amazonaws.com/latest/binaries/gitlab-runner-darwin-arm64 one quickly become throttled which makes the startup cycle to increase drastic +30 minutes
I have two ideas to solve the issue: A. Put the file on company owned s3 bucket. B. Store binary file on the host-os and mount it in after the startup of the vm. This would make the default setup of the Cilicon, more stable.
Do we have any idea of how to start implementing option B? I suppose this is the issue for all the runners and not explicit gitlab. I can try to implement it but currently don't know where to start, unless I go with option A.