[GH-ISSUE #1114] Issue: reusable workflows not supported #636

Closed
opened 2026-03-01 21:45:07 +03:00 by kerem · 2 comments
Owner

Originally created by @ljharb on GitHub (Apr 7, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1114

System information

- Operating System: Mac
- Architecture: x64
- Apple M1: no
- Docker version: 20.10.14
- Docker image used in `act`: medium?
- `act` version: act version 0.2.26

Expected behavior

Run my tests.

Actual behavior

$ act
? Please choose the default image you want to use with act:

  - Large size image: +20GB Docker image, includes almost all tools used on GitHub Actions (IMPORTANT: currently only ubuntu-18.04 platform is available)
  - Medium size image: ~500MB, includes only necessary tools to bootstrap actions and aims to be compatible with all actions
  - Micro size image: <200MB, contains only NodeJS required to bootstrap actions, doesn't work with all actions

Default image and other options can be changed manually in ~/.actrc (please refer to https://github.com/nektos/act#configuration for additional information about file structure) Medium
ERRO[0006] failed to obtain container engine info: Error response from daemon: dial unix $HOME/Library/Containers/com.docker.docker/Data/docker.raw.sock: connect: connection refused 
ERRO[0006] 'runs-on' key not defined in Tests: node.js < 10/tests 
ERRO[0006] 'runs-on' key not defined in Tests: node.js < 10/tests 
ERRO[0006] 'runs-on' key not defined in Tests: pretest/posttest/tests 
ERRO[0006] 'runs-on' key not defined in Tests: pretest/posttest/tests 
ERRO[0006] 'runs-on' key not defined in Tests: node.js >= 10/tests 
ERRO[0006] 'runs-on' key not defined in Tests: node.js >= 10/tests 
ERRO[0006] failed to obtain container engine info: Error response from daemon: dial unix $HOME/Library/Containers/com.docker.docker/Data/docker.raw.sock: connect: connection refused 

Workflow and/or repository

github.com/inspect-js/has-package-exports@76fd1e7307/.github/workflows

Steps to reproduce

  1. Clone the repo
  2. check out the temp branch, or the SHA above
  3. run act

act output

See "actual behavior" above.

Basically, I don't need "runs-on" in the main workflow, because the workflow it references already defines it.

Originally created by @ljharb on GitHub (Apr 7, 2022). Original GitHub issue: https://github.com/nektos/act/issues/1114 ## System information - Operating System: Mac - Architecture: x64 - Apple M1: no - Docker version: 20.10.14 - Docker image used in `act`: medium? - `act` version: act version 0.2.26 ## Expected behavior Run my tests. ## Actual behavior ```sh $ act ? Please choose the default image you want to use with act: - Large size image: +20GB Docker image, includes almost all tools used on GitHub Actions (IMPORTANT: currently only ubuntu-18.04 platform is available) - Medium size image: ~500MB, includes only necessary tools to bootstrap actions and aims to be compatible with all actions - Micro size image: <200MB, contains only NodeJS required to bootstrap actions, doesn't work with all actions Default image and other options can be changed manually in ~/.actrc (please refer to https://github.com/nektos/act#configuration for additional information about file structure) Medium ERRO[0006] failed to obtain container engine info: Error response from daemon: dial unix $HOME/Library/Containers/com.docker.docker/Data/docker.raw.sock: connect: connection refused ERRO[0006] 'runs-on' key not defined in Tests: node.js < 10/tests ERRO[0006] 'runs-on' key not defined in Tests: node.js < 10/tests ERRO[0006] 'runs-on' key not defined in Tests: pretest/posttest/tests ERRO[0006] 'runs-on' key not defined in Tests: pretest/posttest/tests ERRO[0006] 'runs-on' key not defined in Tests: node.js >= 10/tests ERRO[0006] 'runs-on' key not defined in Tests: node.js >= 10/tests ERRO[0006] failed to obtain container engine info: Error response from daemon: dial unix $HOME/Library/Containers/com.docker.docker/Data/docker.raw.sock: connect: connection refused ``` ## Workflow and/or repository https://github.com/inspect-js/has-package-exports/tree/76fd1e7307042d4a2217f2dff72b6c18a39bb9fd/.github/workflows </details> ## Steps to reproduce 1. Clone the repo 1. check out the `temp` branch, or the SHA above 1. run `act` ## `act` output See "actual behavior" above. Basically, I don't need "runs-on" in the main workflow, because the workflow it references already defines it.
kerem 2026-03-01 21:45:07 +03:00
  • closed this issue
  • added the
    kind/bug
    label
Author
Owner

@ChristopherHX commented on GitHub (Apr 7, 2022):

Composite Actions, this is supported != reusable workflows, this not

Duplicates #826

<!-- gh-comment-id:1092108597 --> @ChristopherHX commented on GitHub (Apr 7, 2022): Composite Actions, this is supported != reusable workflows, this not Duplicates #826
Author
Owner

@ljharb commented on GitHub (Apr 7, 2022):

ah, thanks for correcting my terminology, and the pointer to the issue.

<!-- gh-comment-id:1092108865 --> @ljharb commented on GitHub (Apr 7, 2022): ah, thanks for correcting my terminology, and the pointer to the issue.
Sign in to join this conversation.
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#636
No description provided.