Open codeninja opened 1 year ago
Any updates on this? Act looks kinda cool but it seems it is not working :/
Thanks to https://github.com/nektos/act/discussions/1165#discussioncomment-2772110 , we have a workaround:
docker login --username your_username_here
docker pull node:16-buster-slim
Then act should work :)
any updates on this?
I tried this but sadly it didn't work for me
what i noticed is it is not hanging it is just taking some time to download the image, the image size is about image=catthehacker/ubuntu:act-latest
is about 1.2GB
i noticed this when i tried to pull the image will docker cli
docker pull image=catthehacker/ubuntu:act-latest
and after it finished, act
worked fine
@codeninja How does the workload_identity_provider work in act locally?
i got below
[GCP Deploy Infrastructure/infra-deploy]
❗ ::error::google-github-actions/auth failed with: retry function failed after 4 attempts:
gitHub Actions did not inject $ACTIONS_ID_TOKEN_REQUEST_TOKEN or $ACTIONS_ID_TOKEN_REQUEST_URL into this job.
This most likely means the GitHub Actions workflow permissions are incorrect, or this job is being run from a fork. For more information,
please see https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token
I am still facing the same issues.
If I run
act -P ubuntu-latest=nektos/act-environments-ubuntu:18.04 -W .github/workflows/
If I run
act -W .github/workflows/
Any updates or fixes to this?
Using act -v
has a bit too much docker pull progress logging and that is older than this issue.
e.g. the current issue template suggests an act cli command with -v as well, while this issue doesn't mentioned verbose mode anywhere.
Not on my backlog, I'm labeling as confirmed not planned
@ChristopherHX - yeah, noticed the same. Any workaround to this?
Bug report info
Command used with act
Describe issue
Act command fails due to broken build in the docker image. DOcker hub refuses to pull.
Relevant log output
Additional information
No response