3 ms·
I feel your pain, as it's my pain too. Right now we have a pool of gitlab runners running as dedicated virtual machines but on the to-do list I have to test wh
by znpy 5y ago
I feel your pain, as it's my pain too.
Right now we have a pool of gitlab runners running as dedicated virtual machines but on the to-do list I have to test whether rootless podman + gitlab runner cache + $DOCKER_HOST pointing to podman's sock file can let developers use plain old docker-compose and the general docker tooling... Within a dumb pod in a kubernetes clusters, with all the bells and whistles (especially cluster autoscaling).
A man can dream.
Edit: we are a bit advantaged because we run on openstack, run our own registry (harbor) and our cloud provider doesn't charge us for bandwidth...
- mikepurvis 5y agoI'm a huge fan of the kubernetes runner for GitLab CI, but I really wish there was a way to just to `image: path/in/repo/to/Dockerfile` and have it do the right thing as far as creating/using the supplied image.
- deastman 5y agoCan you open an issue in the gitlab-runner project? It would be great if one of our engineers that focuses on the Kubernetes executor can weigh in. https://gitlab.com/gitlab-org/gitlab-runner/-/issues https://gitlab.com/gitlab-org/gitlab-runner/-/issues
- mikepurvis 5y agoSure, done: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28195 https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28195