Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gitlab CI Fails #1530

Open
t-moe opened this issue Jul 23, 2024 · 5 comments
Open

Gitlab CI Fails #1530

t-moe opened this issue Jul 23, 2024 · 5 comments

Comments

@t-moe
Copy link

t-moe commented Jul 23, 2024

Is it possible that the linked FAQ is out of date?

i always get

Error:
0: no container engine found

here is my example repo https://gitlab.com/t-moe/cross-gitlab-ci-test/
with an example run: https://gitlab.com/t-moe/cross-gitlab-ci-test/-/jobs/7403853167

Originally posted by @t-moe in #1507 (comment)

@Emilgardis
Copy link
Member

Do you mean https://github.com/cross-rs/cross/wiki/FAQ#gitlab-ci ? It might be :/

This might be interesting #1351 (comment) however

@t-moe
Copy link
Author

t-moe commented Jul 23, 2024

Yes, I mean that one.

I read that comment, but this also does not resolve the issue:

Using docker image sha256:074f1687a41ccf251dae357352554e41bd8168aecd480acab710389d6f78837d for docker:18.09 with digest docker@sha256:58469a43b529313091f1df424037895a9961b27149aafec812ce8fd8d7ac0c9d ...
$ printenv | grep -v "^HOSTNAME=" > env.list
$ docker run --rm --env-file env.list -v /var/run/docker.sock:/var/run/docker.sock rust:latest bash -c "git clone $CI_REPOSITORY_URL /data && cd /data/ && cross -v build"
docker: error during connect: Post http://docker:2375/v1.39/containers/create: dial tcp: lookup docker on 127.0.0.11:53: no such host.

@Emilgardis
Copy link
Member

try using cross from the main branch

@t-moe
Copy link
Author

t-moe commented Aug 5, 2024

Same or similar error. I've tried various workarounds, listed in the issue tracker. None of them seemd to work. (Sorry for not having them listed out here, for further reference).

In the end I had to pivot to manually invoking cross on my developer machine, because I could not spend more time on this issue :(.

@Emilgardis
Copy link
Member

Sorry you're having issues! I've not experimented with gitlab too much so I'm not super familiar, hopefully I can get some time to look into the woes people are having with it + cross

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants