Not planned
Description
Dear developer,
Since the release of 1.12, our (self-hosted, rootless docker) workflow started failing with:
/opt/conda/bin/python3: can't open file '/home/githubrunner/actions-runner/_work/_actions/pypa/gh-action-pypi-publish/release/v1.12/create-docker-action.py': [Errno 2] No such file or directory
Which seems similar to #291 (the error), but wasn't fixed with the release of 1.12.2
Here's the failing workflow run
https://github.com/SBC-Utrecht/pytom-match-pick/actions/runs/11778522196/job/32805113391#step:7:58
Please let me know if we can help tracking down this issue.
Metadata
Metadata
Assignees
Labels
No labels
Activity
[-]v1.12 still failing with error similar to 291[/-][+]v1.12 still failing with error similar to #291[/+]rjdbcm commentedon Nov 14, 2024
Confirm 1.12.2 still fails for my nested composite action.
webknjaz commentedon Nov 15, 2024
@sroet have you tried checking the contents of
/home/githubrunner/actions-runner/_work/_actions/
? That path is constructed using${{ github.action_path }}
which is supposed to contain a checked out copy of the action, which in turn would havecreate-docker-action.py
in it. And since it's not there, I'd assume a bug in the GitHub Runner software.Also,
/opt/conda/bin/python3
is untypical for usual GH Runners too.ferhatys commentedon Nov 15, 2024
I'm getting the same issue for some reason.
ferhatys commentedon Nov 15, 2024
Confirmed
release/v1.11
is working for me as a workaround.sroet commentedon Nov 15, 2024
Hey @webknjaz, thanks for looking into this!
To repeat: we are running this on self-hosted runners inside a rootless docker, using the continuumio/miniconda3 image.
That image has the default conda installation in
/opt/conda
, this is also where the/opt/conda/bin/python3
comes from.Now for
/home/githubrunner/actions-runner/_work/_actions/
:That directory exists on the host system of the runner, but looking at this line of the setup, specifically:
it seems to get mounted at
/__w/_actions
instead.I don't know enough about creating actions to know if this is a bug in the Runner software or if these variables that are not meant to be used inside actions after the container creation
webknjaz commentedon Nov 15, 2024
Yeah, I understand, but can you check what's actually on dist in the runner host and within container (just add some recursive
ls
or something at the beginning of the job).sroet commentedon Nov 15, 2024
@webknjaz, started a debug workflow in SBC-Utrecht/pytom-match-pick#241. Should we move any back and forth discussion about what folders / variables you want to check to there?
nikaro commentedon Nov 18, 2024
@webknjaz this is a known issue, the workaround seems to be using
$GITHUB_ACTION_PATH
instead of${{ github.action_path }}
.ci: fix pypi publishing job
ci: fix pypi publishing job
ci: fix pypi publishing job
15 remaining items