starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 17:35:49 +03:00

[GH-ISSUE #2357] Adding support for pluggable Container Execution Environments like AWS ECS Fargate and similar #1084

New issue

Open

opened 2026-03-01 21:48:47 +03:00 by kerem · 3 comments

kerem commented

2026-03-01 21:48:47 +03:00

Owner

Originally created by @yuriy-yarosh on GitHub (Jun 9, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2357

Act version

act version 0.2.63

Feature description

Github Actions autoscaling is kinda busted if you don't want to rely on Github Actions Webhooks.
AWS CodeBuild and AWS CodeCatalyst are overpriced, and it makes more sense to replace them with AWS ECS Fargate Spot, or EC2 Spot Fleet Instances.

ACT has a pre-defined workflow graph for jobs that can be traversed and respective resources could be provisioned, autoscaled on demand, or scrapped during idling.

This would make ACT a very convenient tool for those who don't want to dive deep into Kubernetes and prefer to focus on simpler Cloud Managed Solutions.

Originally created by @yuriy-yarosh on GitHub (Jun 9, 2024). Original GitHub issue: https://github.com/nektos/act/issues/2357 ### Act version act version 0.2.63 ### Feature description Github Actions autoscaling is kinda busted if you don't want to rely on Github Actions Webhooks. AWS CodeBuild and AWS CodeCatalyst are overpriced, and it makes more sense to replace them with AWS ECS Fargate Spot, or EC2 Spot Fleet Instances. ACT has a pre-defined workflow graph for jobs that can be traversed and respective resources could be provisioned, autoscaled on demand, or scrapped during idling. This would make ACT a very convenient tool for those who don't want to dive deep into Kubernetes and prefer to focus on simpler Cloud Managed Solutions.

kerem added the

kind/feature-request

label

2026-03-01 21:48:47 +03:00

kerem commented

2026-03-01 21:48:48 +03:00

Author

Owner

@yuriy-yarosh commented on GitHub (Jun 9, 2024):

Shoes have something similar for EC2 Spots, implemented as a hashicorp plugin.

@yuriy-yarosh commented on GitHub (Jun 9, 2024): [Shoes](https://github.com/whywaita/myshoes/tree/master) have something similar for [EC2 Spots](https://github.com/whywaita/shoes-aws/tree/main), implemented as a [hashicorp plugin](https://github.com/whywaita/shoes-aws/blob/main/main.go#L51).

kerem commented

2026-03-01 21:48:48 +03:00

Author

Owner

@ChristopherHX commented on GitHub (Jun 11, 2024):

What is your longterm Goal?, some of solutions are already available in the wild

Some potential Goals are listed here, maybe it's not in the list

replace GitHub Actions completely
- Want to use nektos/act cli with the feature requested here
- my ~~runner.server~~ project, webhook based fake GitHub Actions Server. Not ready outside POC testing.
replace both GitHub and GitHub Actions completely
- => Gitea + Gitea Actions
  - act_runner based on nektos/act for job execution
  - MIT License
  - self-hostable
  - I'm not aware of an autoscaler
replace the GitHub Actions Runner and keep using GitHub Actions
- => github-act-runner
  - Disclaimer my project
  - based on my fork of nektos/act
  - allows to create a pipe shell script to move the job into anything you can pipe stdin/stdout to (maybe complicated to set up), this allows you to execute a fixed/variable count of runners on the same node as long polling listener that creates anything you like if you have something like ssh access
  - can be remote controlled by my fake GitHub Actions backend (runner.server), that doesn't implement sending workflow_job events
  - also can tunnel actions/runner into different containers
  - Could satisfy these requirements taken from linked issue
    
    nothing similar to an external workflow or external execution environments providers.
  - I'm not aware of an autoscaler
    - you might be able to script one with this runner
    - This runner can be created in memory as a go api
    - For example workflow_job webhook based https://github.com/ChristopherHX/megascaler

BTW I don't have the time to implement feature requests

@ChristopherHX commented on GitHub (Jun 11, 2024): What is your longterm Goal?, some of solutions are already available in the wild Some potential Goals are listed here, maybe it's not in the list - replace GitHub Actions completely - Want to use nektos/act cli with the feature requested here - my ~~runner.server~~ project, webhook based fake GitHub Actions Server. Not ready outside POC testing. - replace both GitHub and GitHub Actions completely - => Gitea + Gitea Actions - act_runner based on nektos/act for job execution - MIT License - self-hostable - I'm not aware of an autoscaler - replace the GitHub Actions Runner and keep using GitHub Actions - => github-act-runner - Disclaimer my project - based on my fork of nektos/act - allows to create a pipe shell script to move the job into anything you can pipe stdin/stdout to (maybe complicated to set up), this allows you to execute a fixed/variable count of runners on the same node as long polling listener that creates anything you like if you have something like ssh access - can be remote controlled by my fake GitHub Actions backend (runner.server), that doesn't implement sending workflow_job events - also can tunnel actions/runner into different containers - Could satisfy these requirements taken from linked issue > nothing similar to an external workflow or external execution environments providers. - I'm not aware of an autoscaler - you might be able to script one with this runner - This runner can be created in memory as a go api - For example workflow_job webhook based <https://github.com/ChristopherHX/megascaler> BTW I don't have the time to implement feature requests

kerem commented

2026-03-01 21:48:48 +03:00

Author

Owner

@ErikEngerd commented on GitHub (Nov 10, 2024):

Perhaps implementing container hooks as described here:

https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/customizing-the-containers-used-by-jobs

See for example the k8s hook: https://github.com/actions/runner-container-hooks

@ErikEngerd commented on GitHub (Nov 10, 2024): Perhaps implementing container hooks as described here: https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/customizing-the-containers-used-by-jobs See for example the k8s hook: https://github.com/actions/runner-container-hooks

kerem referenced this issue

2026-03-01 21:52:35 +03:00

[PR #1084] [MERGED] automatically merge PRs from dependabot #1765

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#1084

No description provided.

Rows
Columns