#However it fails at the `go build` stage
still briar
hmm the error doesn't say much.. reproing now
in the meantime maybe we could setup a quick GH workflow to publish a main cloak binary somewhere for these cases? cc @gleaming birch ?
still briar
👋 seems to be working here: https://gitlab.com/marcosnils/ci-test/-/jobs/2982243653
👀
let me make the repo public
done
austere scarab
Thanks
austere scarab
@still briar apart from $GITHUB_USER and $GITHUB_TOKEN did you need to set any other variables or do any additional configuration?
Also could you let me know how you configured your gitlab runner?
still briar
the only thing I changed apart from the env variables is adding the --depth=1 to the git clone to make it faster. One thing to note is that cloak dev needs to be executed as a background job since otherwise it'll block the job execution.
still briar
Also could you let me know how you configured your gitlab runner?
I used gitlab's runners. I don't have a custom one
here's my job definition: https://gitlab.com/marcosnils/ci-test/-/ci/editor?branch_name=main
austere scarab
Yes, I saw it in your repo but somehow it doesn't work for me. I am using a local runner as I don't have access to gitlab runners in my project, so perhaps that's why it fails
still briar
do you see any other piece of information after this line?
that doesn't say much :S
austere scarab
No, unfortunately not and that's why I was not able to proceed - there's no clue why it's failing
Huh, it worked now
github.com/moby/buildkit/util/progress/progresswriter
github.com/moby/buildkit/session/auth/authprovider
github.com/spf13/cobra
github.com/dagger/cloak/engine
github.com/dagger/cloak/cmd/cloak
$ echo foo
foo
Cleaning up project directory and file based variables 00:01
Job succeeded```😕
austere scarab
It was exactly the same script which failed continuously a few minutes before
This is quite weird - but since it is working i will try to proceed and not look a gift horse in the mouth 🙂
still briar
did you add the & to cloak dev or something now?
I have the theory that cloak dev is actually failing but because you added the & now, the pipeline is able to proceed without errors
austere scarab
I did already add the & earlier but it failed previously even with that
still briar
I did already add the & earlier but it failed previously even with that
🤔 interesting.. can you check if cloak is actually running after you start it?
since it might be starting and failing immediately
I'd suggest re-launching your job with debug mode and try to do it manually
austere scarab
It seems you're correct because
Error: exit status 1
/builds/project-0 # docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
that seems to be the issue then. Have you used docker in your local runners before?
seems like docker is not working for some reason
still briar
it does for the gitlab runners.. but seems like in your case it's not quite there. IIRC you need to do some custom configuration to allow your local runners do dind
https://docs.gitlab.com/ee/ci/docker/using_docker_build.html
^ that might help
austere scarab
This was helpful to an extent. I have configured TLS for dind as described in the manual but somehow it does not seem to work and after I log into the container shell, I see a TLS-related error