mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1803] Running ACT hangs when downloading the ac-latest docker image. #881
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#881
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @codeninja on GitHub (May 12, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1803
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
@ennioVisco commented on GitHub (Aug 12, 2023):
Any updates on this? Act looks kinda cool but it seems it is not working :/
@ennioVisco commented on GitHub (Aug 22, 2023):
Thanks to https://github.com/nektos/act/discussions/1165#discussioncomment-2772110 , we have a workaround:
Then act should work :)
@NavidBecause commented on GitHub (Jan 6, 2024):
any updates on this?
I tried this but sadly it didn't work for me
@Omarabdul3ziz commented on GitHub (Mar 13, 2024):
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-latestis about 1.2GBi noticed this when i tried to pull the image will docker cli
and after it finished,
actworked fine@RS185734 commented on GitHub (Mar 24, 2024):
@codeninja How does the workload_identity_provider work in act locally?
i got below
@kirtimanmishrazipstack commented on GitHub (Jul 16, 2024):
I am still facing the same issues.
If I run
act -P ubuntu-latest=nektos/act-environments-ubuntu:18.04 -W .github/workflows/<workflow-name.yaml>
It is stuck at docker pull image=nektos/act-environments-ubuntu:18.04 platform= username= forcePull=false
If I run
act -W .github/workflows/<workflow-name.yaml>
It is stuck at docker pull image=catthehacker/ubuntu:full-latest platform= username= forcePull=true
@varun-hopstack commented on GitHub (Sep 27, 2024):
Any updates or fixes to this?
@ChristopherHX commented on GitHub (Sep 27, 2024):
Using
act -vhas 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
@varun-hopstack commented on GitHub (Sep 30, 2024):
@ChristopherHX - yeah, noticed the same. Any workaround to this?
@rj-wowza commented on GitHub (Feb 11, 2025):
It's just reaaly slow the first time it runs; mine took about 10 mins. After it is cached it will run faster.
@rajinder-yadav commented on GitHub (Sep 2, 2025):
I can confirm it takes a long time to download image (I selected large), but it's running fine for me.
I stopped and started 'act' two times until I came across this issue and read @rj-wowza message!
@Xander-MartinLvl commented on GitHub (Oct 15, 2025):
Can confirm that it takes a while. There should probably be more visibility that things are moving aside from -v.