mirror of
https://github.com/nektos/act.git
synced 2026-04-26 17:35:49 +03:00
[GH-ISSUE #1151] Issue: yq missing from path in act, not missing on github #647
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#647
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 @therealmitchconnors on GitHub (May 5, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1151
The following config assumes
yqis on the path in bash, and that assumption works when running on GitHub, but fails with act. Is there a known difference in the ubuntu-latest versions supported by GitHub and act?The output of the above is:
System information
Expected behaviour
yqis on the pathActual behaviour
yqis not on the pathWorkflow and/or repository
see above
Steps to reproduce
use above worfklow
actoutput@catthehacker commented on GitHub (May 6, 2022):
yqis not included in the image: https://github.com/nektos/act#default-runners-are-intentionally-incomplete@david-dest01 commented on GitHub (Feb 16, 2024):
can we make it available?
@ChristopherHX commented on GitHub (Feb 16, 2024):
The "large" image should have it
See https://nektosact.com/usage/runners.html#runners
act -v -P ubuntu-latest=catthehacker/ubuntu:full-latest, (act won't log anything durng pull without-v, that can take spme time for 17GB to be downloaded and unpacked to ca. 57GB)Making medium a second large image doesn't seem to make sense for me.
@david-dest01 commented on GitHub (Feb 16, 2024):
ugly but effective - appreciate the response @ChristopherHX