# K3os and GitLab Runner integration

**URL:** <https://forums.suse.com/t/k3os-and-gitlab-runner-integration/17964>\
**Category:** k3s, k3OS, and k3d\
**Created:** [July 15, 2020, 11:54am UTC](https://forums.suse.com/t/k3os-and-gitlab-runner-integration/17964 "2020-07-15T11:54:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![guy](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/guy/32/4932_2.png) [@guy](https://forums.suse.com/u/guy)\
**Post date:** [July 15, 2020, 11:54am UTC](https://forums.suse.com/t/k3os-and-gitlab-runner-integration/17964/1 "2020-07-15T11:54:42Z")

</div>

I’ve installed k3os on metal, I’ve then pointed my Gitlab to the kubernetes cluster.

i’m able to install Helm Tiller via gitlab, I then go on to install “GitLab Runner”.

However that’s where things fail. I commit new code and the CI picks up the job and tries to swamp a container to build the project. This fails as it’s not able to find docker.

docker build -t $CONTAINER\_BRANCH\_IMAGE .

[41](https://gitlab.home.net/Home/dns-master/-/jobs/3137#L41) time=“2020-07-15T10:38:52Z” level=error msg=“failed to dial gRPC: cannot connect to the Docker daemon. Is ‘docker daemon’ running on this host?: dial unix /var/run/docker.sock: connect: no such file or directory”

[42](https://gitlab.home.net/Home/dns-master/-/jobs/3137#L42) error during connect: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.40/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&session=py8ctit3ac1jwt56jlfafoww3&shmsize=0&[t=gitlab.int.britewhite.net](http://t=gitlab.int.britewhite.net)%3A5005%2Fhome%2Fdns-master%3Amaster&target=&ulimits=null&version=1: context canceled

[44](https://gitlab.home.net/Home/dns-master/-/jobs/3137#L44)Running after\_script

00:00

[46](https://gitlab.home.net/Home/dns-master/-/jobs/3137#L46)Uploading artifacts for failed job

00:00

[48](https://gitlab.home.net/Home/dns-master/-/jobs/3137#L48) ERROR: Job failed: command terminated with exit code 1

So in a K3os world how do we make use of gitlab runner to build docker containers?

Thanks  
–Guy

---

<div class="post-metadata">

**Author:** ![gbonnefille](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/gbonnefille/32/6581_2.png) [@gbonnefille](https://forums.suse.com/u/gbonnefille)\
**Post date:** [August 5, 2020, 9:01am UTC](https://forums.suse.com/t/k3os-and-gitlab-runner-integration/17964/2 "2020-08-05T09:01:50Z")

</div>

Personnally, I switched from `docker build` to kaniko, as suggested in the Gitlab’s documentation: [https://docs.gitlab.com/ce/ci/docker/using\_kaniko.html](https://docs.gitlab.com/ce/ci/docker/using_kaniko.html)

---

<div class="post-metadata">

**Author:** ![cloudy\_days](https://avatars.discourse-cdn.com/v4/letter/c/7bcc69/32.png) [@cloudy\_days](https://forums.suse.com/u/cloudy_days)\
**Post date:** [February 20, 2022, 1:39pm UTC](https://forums.suse.com/t/k3os-and-gitlab-runner-integration/17964/3 "2022-02-20T13:39:29Z")

</div>

Curious if you’re using GitLabs “cloud native” images: [GitLab.org / Build / CNG · GitLab](https://gitlab.com/gitlab-org/build/CNG)  
Or their default chef-based “omnibus”?

---

<div class="post-metadata">

**Author:** ![gbonnefille](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/gbonnefille/32/6581_2.png) [@gbonnefille](https://forums.suse.com/u/gbonnefille)\
**Post date:** [February 22, 2022, 9:11am UTC](https://forums.suse.com/t/k3os-and-gitlab-runner-integration/17964/4 "2022-02-22T09:11:10Z")

</div>

We have multiple Gitlab, running from K8S, Omnibus or Docker. Gitlab-runner are generally running on K3OS so with the Docker images provided by Gitlab.