| *** toscalix has joined #trustable | 08:59 | |
| *** toscalix has quit IRC | 09:00 | |
| *** ecclescake has joined #trustable | 09:13 | |
| *** toscalix has joined #trustable | 09:23 | |
| ikerperez | I am back to fossology still thinking how to run the docker container in the CI, after ctgriffiths's recommendation of using socket binding for that instead of running docker-in-docker, jjardon recommended me to have a look to this: https://docs.gitlab.com/ee/ci/docker/using_docker_build.html | 10:34 |
|---|---|---|
| ikerperez | In there there is a step for socket binding and explains how I need to configure the gitlab runner and other steps before work in the actual CI. Can I do that myself or do I any privileges? | 10:37 |
| ikerperez | As well there is this step https://docs.gitlab.com/ee/ci/docker/using_docker_build.html#use-shell-executor | 10:37 |
| ikerperez | I would like to know if that would be more suitable or if it is how docket is implemented in the CI at first place | 10:38 |
| ikerperez | I mean like the base fedora Image is running now | 10:38 |
| ikerperez | standup https://gitlab.com/trustable/distros/overview/wikis/2018-11-07 | 10:45 |
| ctgriffiths | ikerperez: flatmush can give you access to the runner if you don't have it already. I'd stick with docker rather than the shell executor as I don't think it will be a quick change. You'll have to manage the user priviledges, like docker access, on the host and all the tools become host dependencies rather than being installed before each build | 11:04 |
| ctgriffiths | also you may have to manually clear the buildstream cache before each build when using the shell executor as I think it will persist, though I'm not 100% sure on that | 11:05 |
| ikerperez | ok, I stick to the docker socket method then. thanks ctgriffiths | 11:06 |
| ikerperez | I will need to install the gitlab runner so I guess that I will need access to the server | 11:39 |
| ikerperez | and to register GitLab Runner from the command line to use docker and share /var/run/docker.sock | 11:41 |
| ctgriffiths | the server already has gitlab runner, gitlab runner currently creates the fedora docker container that then runs the build and test | 11:41 |
| ctgriffiths | so you need to change the exisitng configuration | 11:41 |
| ikerperez | ok, so how can I connect to the server? | 12:22 |
| ikerperez | flatmush ^^ | 12:53 |
| flatmush | ikerperez: I'm not sure what you want to do with the server | 12:58 |
| ikerperez | flatmush this steps https://github.com/fossology/fossology.git | 12:59 |
| ikerperez | sorry | 12:59 |
| ikerperez | not that | 12:59 |
| ikerperez | https://docs.gitlab.com/ee/ci/docker/using_docker_build.html#use-docker-socket-binding | 12:59 |
| flatmush | you want to re-register the runner? | 13:01 |
| flatmush | ok, I'll give you a login on it, one sec | 13:02 |
| ikerperez | yes | 13:05 |
| ikerperez | ok | 13:05 |
| flatmush | I have to wait for operations to give me shell or vpn access, since I'm wfh | 13:06 |
| flatmush | apparently we don't have that by default | 13:06 |
| * flatmush gives ikerperez access to the server | 15:05 | |
| *** ecclescake has quit IRC | 17:35 | |
| *** toscalix has quit IRC | 18:55 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!