IRC logs for #cip for Friday, 2019-07-19

*** vidda has joined #cip01:38
*** therisen has joined #cip06:29
*** rajm has joined #cip06:56
*** binhnk has joined #cip06:59
*** therisen has quit IRC07:50
*** therisen has joined #cip07:53
patersoncHello all08:04
therisenhi patersonc08:18
patersoncHow's it going?09:05
patersoncSorry for the slow reply, just in the CIP Kernel meeting09:06
patersoncThank you for trying with the linux-cip-ci issues09:10
patersoncCan you think of another solution to using "DOCKER_HOST: tcp://localhost:2375" in gitlab-ci.yml?09:11
patersoncIt breaks usage with the gitlab shared runners09:11
ironfootgitlab shared runners can run docker. Where is this .gitlab-ci.yml file?09:27
patersonchttps://gitlab.com/cip-playground/linux-cip-ci/blob/master/.gitlab-ci.yml09:31
patersoncI need to set DOCKER_HOST when using the CIP gitlab runner setup by therisen, but it's not needed for the gitlab shared runners09:32
patersoncThe cip runner is in a kubernetes pod btw09:40
ironfootso, this is to get the CI working on any forks?09:42
ironfootor to stop depending on self hosted runners, right?09:44
ironfootah, I understand the problem now. Why not always use the shared ones?09:48
patersoncBecause we have our own ;) plus they are slower ;)09:50
therisenironfoot: shared runners do not allow privileged containers which we need for ISAR-based builds.10:12
therisenpatersonc: how about managing /etc/hosts dynamically?10:13
*** toscalix has joined #cip10:14
therisenalso take a look at hostAliases here: https://gitlab.com/charts/gitlab-runner/blob/master/values.yaml however, i don't think these settings are applied to the actual pods used to build the pods...10:23
*** toscalix has quit IRC10:28
*** vidda has quit IRC11:17
patersonctherisen: I'll take a look when I'm back from Japan13:36
patersoncThanks13:36
*** therisen has quit IRC13:54
*** rajm has quit IRC22:12

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!