-
Notifications
You must be signed in to change notification settings - Fork 390
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
Docker-in-Docker GitLab CI #513
Comments
Gitlab runner set a different hostname, which is not equal to conatiner name. eg:
In cross, we assume that hostname is equal to container name: I have not find a solution yet. |
Workaround: script:
- export HOSTNAME=$(docker ps -ql)
- cross build ... |
Calling |
That suggests there are no created containers, of any state (running or stopped). Try using |
This is a duplicate of #273. We've documented how to use docker-in-docker, remote docker (required if Gitlab is using a remote Docker connection, such as with a host at |
This didn't work for me when I had multiple cross builds running in parallel. I got around it by doing this instead: script:
- export HOSTNAME=$(docker ps -aqf "name=^$HOSTNAME" | awk 'NR==1{print $1}')
- cross build ... |
I am using
cross
in a docker-in-docker scenario on GitLab CI. I used the approach given in #273 (comment), which unfortunately did not work anymore. I am still getting:So I used
CROSS_DOCKER_IN_DOCKER=true
(as recommended in another comment) and the result is this:I have the latest release of cross installed (but checking a diff with
master
didn't reveal relevant changes as far as I can tell).I am wondering why this does not work in the GitLab environment...
Thanks in advance!
The text was updated successfully, but these errors were encountered: