1 reply
.cargo-home and caching that, but I don't know if that's really the only way; I previously tried to cache /root/.cargo, /usr/local/cargo and some others; so I guess my question is: Can plugins not access directories outside of the project dir, or am I looking in the wrong place? (I haven't tried $HOME/.cargo yet, maybe that would work)
To be clear, the exact directories I tried to cache were:
- /root/.cargo
- /usr/local/cargo
- ~/.cargo
For every single one of them, the plugin told me that it doesn't exist.
POST /api/repos/{namespace}/{name}/builds (https://docs.drone.io/api/builds/build_create/), but i receive: "message": "invalid character 'b' looking for beginning of value". Running a specific build POST /api/repos/{namespace}/{name}/builds/NUMBER, it works. Is this a bug, or do i understand the docs wrong?
3 replies
docker run command you used to install the runner so we can advise further?
docker run -d \
-v /var/run/docker.sock:/var/run/docker.sock \
-e DRONE_RPC_PROTO=https \
-e DRONE_RPC_HOST=www.mysite.com \
-e DRONE_RPC_SECRET=super-duper-secret \
-e DRONE_RUNNER_CAPACITY=2 \
-e DRONE_RUNNER_NAME=mysite.com \
-p 3000:3000 \
--restart always \
--name drone-runner \
drone/drone-runner-docker:1
Cannot connect to the Docker daemon ... means that Drone cannot read /var/run/docker.sock
- do you see
/var/run/docker.sockon the host? if it is not there, where is it? - do you have generic issues connecting to the host docker daemon
docker run -v /var/run/docker.sock:/var/run/docker.sock docker /bin/sh -c "docker ps"
@bradrydzewski
1) it's there just seems to be empty
2) This is my output:
user@localhost:~$ docker run -v /var/run/docker.sock:/var/run/docker.sock docker /bin/sh -c "docker ps"
Unable to find image 'docker:latest' locally
latest: Pulling from library/docker
801bfaa63ef2: Already exists
4f7dc993c79e: Pull complete
d39d95e4997f: Pull complete
ae283de69b7d: Pull complete
1962c7344fe5: Pull complete
aa7a3367c785: Pull complete
5e259227d438: Pull complete
Digest: sha256:73ca622074aa007422a60cc1bfd4e65ca3ee8842e794df54cd1c3be3069d31bf
Status: Downloaded newer image for docker:latest
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b46dea41075e docker "docker-entrypoint.s…" Less than a second ago Up Less than a second keen_cohen
bea8e70d2eb3 drone/drone-runner-docker:1 "/bin/drone-runner-d…" 7 minutes ago Up 7 minutes 0.0.0.0:3000->3000/tcp drone-runner
3ad9eee92324 drone/drone:1 "/bin/drone-server" 7 minutes ago Up 7 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp drone
https://docs.drone.io/runner/kubernetes/configuration/policies/
This does not have documentation on the match field.
Seems like the first policy is applied to all builds even if we have match for certain repositories.
2 replies
curl -i https://drone.example.com/api/repos/orgslug/reposlug/builds\?branch\=main -X POST \
-H "Authorization: Bearer xxxxxxxxx" in my terminal fairly often. IIRC drone-cli also could do something similar.
.drone.yml - One of them depends_on the previous two, however it should also run if either of those two fails, it's basically a clean up step that should always run at the very end. I tried setting when: status: failure, success on a pipeline level and also on a step level. But neither seems to have an effect. If either of the previous two pipelines fail, the last step is skipped. Am I missing something, not doing it right or is this setup currently not possible?
1 reply
