Closed beeb closed 9 months ago
I also tried to configure the checkout action to checkout the main branch (to get the latest commit that triggered the workflow) and fetch-depth: 0
like in the readme but it didn't make a difference.
Please also note that building from source in CI (with cargo install) and running the command without docker works fine. It's only the container version that fails like above.
Weird, how can I reproduce this? Also, did you get this error for the recently released version (2.0.6
) or was it always there?
The reproduce, you can try the following. Spin up a self-hosted runner with this docker command:
docker run -it --name my-runner \
-e RUNNER_NAME=my-runner \
-e GITHUB_ACCESS_TOKEN=your_PAT_token \
-e RUNNER_REPOSITORY_URL=https://github.com/... \
-v /var/run/docker.sock:/var/run/docker.sock \
tcardonne/github-runner:ubuntu-20.04
More info at https://github.com/tcardonne/docker-github-runner
Then you can start a workflow in that repository you linked in the command above, using the git-cliff action. You should see the error like me.
To use the self-hosted runner, make sure you put runs-on: [self-hosted, linux]
I just started using git-cliff so I have no prior experience with older versions.
Later today or tomorrow I will try to switch to https://github.com/myoung34/docker-github-actions-runner to see if it makes a difference.
Same story with the other self-hosted runner, I think it should be reproducible if you try running either of those containers and run the action on them.
Hey again, sorry for the late reply. I recently released the new version of git-cliff
and updated this action accordingly. Is this still an issue?
Hey @orhun thanks for getting back to this issue. I don't have access to a self-hosted runner anymore since I switched jobs. If I get the chance I'll try to spin up one and set up one of my repos to use it, but it might be a while until I can
Okay, just let me know!
@orhun I updated to v2.2.0 from v2.0.0 and that fixed the issue. It looks like v2.0.0 is gone or something:
/usr/bin/docker build -t 1906d0:27cb555a07d84bdea80da72f1e6516e0 -f "/home/runner/work/_actions/orhun/git-cliff-action/v2/Dockerfile" "/home/runner/work/_actions/orhun/git-cliff-action/v2"
#0 building with "default" instance using docker driver
#1 [internal] load .dockerignore
#1 transferring context: 2B done
#1 DONE 0.0s
#2 [internal] load build definition from Dockerfile
#2 transferring dockerfile: 620B done
#2 DONE 0.0s
#3 [internal] load metadata for docker.io/orhunp/git-cliff:1.4.0@sha256:5642cc7ac848a79f021056c4903f01d1447d10236561b97b6db3b57f5fac5536
#3 ...
#4 [auth] orhunp/git-cliff:pull token for registry-1.docker.io
#4 DONE 0.0s
#3 [internal] load metadata for docker.io/orhunp/git-cliff:1.4.0@sha256:5642cc7ac848a79f021056c4903f01d1447d10236561b97b6db3b57f5fac5536
#3 ERROR: failed to do request: Head "https://registry-1.docker.io/v2/orhunp/git-cliff/manifests/sha256:5642cc7ac848a79f021056c4903f01d1447d10236561b97b6db3b57f5fac5536": EOF
Thank you for git-cliff btw. Its great.
Hmm interesting. I'm glad it is fixed though 🐻
Trying to use the action with self-hosted runners running in docker. I am not sure if this issue is related to having to use "docker in docker". I know for instance that when using
cross-rs
in my self-hosted runners I need to enable a flag for docker in docker.Note that the only step before this one is using
actions/checkout@v3
with defaults.