[GH-ISSUE #2711] Spin up service containers when using host executor #1227

New issue

Open

opened 2026-03-01 21:49:48 +03:00 by kerem · 0 comments

kerem commented

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

Owner

Originally created by @chibidev on GitHub (Mar 24, 2025).
Original GitHub issue: https://github.com/nektos/act/issues/2711

Act version

act version 0.2.74

Feature description

Currently, service containers defined for the workflow seem to be only evaluated and brought up when the workflow is executed within the runner container. Specifying -P xyz=-self-hosted removes this convenience and requires additional measures to create the same execution context.

Since changing this behavior might end-up breaking current scripts, I'm thinking whether adding a new command line switch (e.g. --with-services, although I'm pretty sure someone far smarter than me can come up with a better name) to opt-into this convenience would be something the current maintainers might consider.

Happy to contribute myself, if the approach seems reasonable, I just wanted to test the waters first.

Originally created by @chibidev on GitHub (Mar 24, 2025). Original GitHub issue: https://github.com/nektos/act/issues/2711 ### Act version act version 0.2.74 ### Feature description Currently, service containers defined for the workflow seem to be only evaluated and brought up when the workflow is executed within the runner container. Specifying `-P xyz=-self-hosted` removes this convenience and requires additional measures to create the same execution context. Since changing this behavior might end-up breaking current scripts, I'm thinking whether adding a new command line switch (e.g. `--with-services`, although I'm pretty sure someone far smarter than me can come up with a better name) to opt-into this convenience would be something the current maintainers might consider. Happy to contribute myself, if the approach seems reasonable, I just wanted to test the waters first.

kerem added the

kind/feature-request

label

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

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

No description provided.

Rows
Columns