-
Notifications
You must be signed in to change notification settings - Fork 7
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
Git missing from docker image? #2
Comments
Git should be installed in mattgruter/doubledocker (gets installed by lxc-docker, see https://get.docker.io/ubuntu/). Have you changed anything when building the Dockerfile? |
Nope pulled the image straight from the registry. Perhaps something changed further down the image chain? I will delete the image from my machine and pull again. |
@jwmarshall any luck? |
Haven't tried again, got pull away to other projects. Will try to spin up some drones again towards the end of the week. |
I had the same issue when using the bradrydzewski/ubuntu image. I don't have it anymore when using the bradrydzewski/gcc:4.8 image. |
I've the same issue with the latest drone.deb file. When I enter the running container (using docker exec or docker-enter) I can execute git within the container. Then I replaced /usr/bin/local/drone with a simple shell-script which only dumps PATH and LD_LIBRARY_PATH. Even after restarting droned (inside the same container!) and triggering the build via Web UI the error message remains. It's a bit strange, because I've replaced /usr/bin/local/drone and thus the original file is removed from the container. The error message is still the same: |
I have the same issue. |
have you resolved it? .. having the same issue |
I think it's because git has been removed from the base drone ubuntu image. I've raised an issue https://github.com/drone/images/issues/43 update Ok, I was using ubuntu as my image, changing to bradrydzewski/base resolves the missing git |
Pretty sure this worked before, not sure what happened.
/usr/local/bin/drone: line 34: git: command not found
The text was updated successfully, but these errors were encountered: