starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 09:25:54 +03:00

[GH-ISSUE #88] Consider using actions/runner #57

New issue

Closed

opened 2026-03-01 21:39:32 +03:00 by kerem · 3 comments

kerem commented

2026-03-01 21:39:32 +03:00

Owner

Originally created by @cplee on GitHub (Feb 20, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/88

(from PR #84)

@marcosnils

Seems like you did an amazing work and effort to implements all this features. The way what I thought about implementing this local runner is to actually use the open source runner (https://github.com/actions/runner) that already has all the logic on how to run and process the workflow yaml files. I'd love to know if you thought about that approach and if so, the main reasons why you chose to implement it yourself. If you believe we can use the open source runner instead, I already did some work around that that I'd like to share.

@cplee

I did look at it as my first approach. Ran it locally and captured the API traffic back to GitHub from the runner. The API is very chatty, verbose....and undocumented. Lots of references to VSTS in the API payloads 🤯Looked much more difficult to simulate the API between the runner and GH so I went the direction I did. Would love to hear more about your learnings and I'm happy to reconsider!

@marcosnils

I haven't checked in detail, but I only saw that the listener can be invoked in something that's called local run (github.com/actions/runner@6c70d53eea/src/Misc/layoutroot/run.sh (L23-L27)). I was hoping that option could actually help running stuff locally without having to interact with the VSTS or GH API. Seems like you have better understanding about the runner internals and it might be a dead end?

@cplee

Looks like it has potential...that's the right idea. Can't find any details on how that works though... 🤔

@marcosnils

Maybe @TingluoHuang can help us here?

Originally created by @cplee on GitHub (Feb 20, 2020). Original GitHub issue: https://github.com/nektos/act/issues/88 (from [PR #84](https://github.com/nektos/act/pull/84#issuecomment-589245950)) @marcosnils > Seems like you did an amazing work and effort to implements all this features. The way what I thought about implementing this local runner is to actually use the open source runner (https://github.com/actions/runner) that already has all the logic on how to run and process the workflow yaml files. I'd love to know if you thought about that approach and if so, the main reasons why you chose to implement it yourself. If you believe we can use the open source runner instead, I already did some work around that that I'd like to share. @cplee > I did look at it as my first approach. Ran it locally and captured the API traffic back to GitHub from the runner. The API is very chatty, verbose....and undocumented. Lots of references to VSTS in the API payloads 🤯Looked much more difficult to simulate the API between the runner and GH so I went the direction I did. Would love to hear more about your learnings and I'm happy to reconsider! @marcosnils > I haven't checked in detail, but I only saw that the listener can be invoked in something that's called local run (https://github.com/actions/runner/blob/6c70d53eead402ba5d53676d6ed649a04e219c9b/src/Misc/layoutroot/run.sh#L23-L27). I was hoping that option could actually help running stuff locally without having to interact with the VSTS or GH API. Seems like you have better understanding about the runner internals and it might be a dead end? @cplee > Looks like it has potential...that's the right idea. Can't find any details on how that works though... 🤔 @marcosnils > Maybe @TingluoHuang can help us here?

kerem

2026-03-01 21:39:32 +03:00

closed this issue
added the
stale

kind/question

area/runner
labels

kerem commented

2026-03-01 21:39:33 +03:00

Author

Owner

@ghost commented on GitHub (Apr 24, 2020):

傳自 iPhone 版的 Yahoo奇摩電子信箱

於星期五, 4月 24, 2020, 08:06，github-actions[bot] notifications@github.com 寫道：

Closed #88.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@ghost commented on GitHub (Apr 24, 2020): 傳自 iPhone 版的 Yahoo奇摩電子信箱於星期五, 4月 24, 2020, 08:06，github-actions[bot] <notifications@github.com> 寫道： Closed #88. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

kerem commented

2026-03-01 21:39:33 +03:00

Author

Owner

@marcosnils commented on GitHub (Apr 24, 2020):

What??? @cplee this got closed very strangely

@marcosnils commented on GitHub (Apr 24, 2020): What??? @cplee this got closed very strangely

kerem commented

2026-03-01 21:39:33 +03:00

Author

Owner

@torbjornvatn commented on GitHub (May 15, 2020):

@cplee here's a dockerified version of the local runner that might be interesting to consider https://github.com/myoung34/docker-github-actions-runner

@torbjornvatn commented on GitHub (May 15, 2020): @cplee here's a dockerified version of the local runner that might be interesting to consider https://github.com/myoung34/docker-github-actions-runner

kerem referenced this issue

2026-03-01 21:50:46 +03:00

[PR #57] [MERGED] Use docker’s stdcopy to ensure we don’t emit garbage bytes to stdout #1342

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#57

No description provided.

Rows
Columns