mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2086] run-vcpkg fails on latest ubuntu full image #998
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#998
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 @eladm-ultrawis on GitHub (Nov 10, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/2086
Bug report info
Command used with act
Describe issue
When I run it on ubuntu-22.04 it succeeds. however if I use the act latest and full image it fails:
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@eladm-ultrawis commented on GitHub (Nov 10, 2023):
link to the issue on run-vcpkg repo:
https://github.com/lukka/run-vcpkg/issues/213
@ChristopherHX commented on GitHub (Nov 10, 2023):
Hmm, this seem to be a bug of non root container support in act...
I didn't make act to grant non root write access to parent folders of your workspace
The actions tries to access files outside of the workspace folder (_work of actions/runner), which are still owned by root.
Something like, after actions/checkout
should help you for the next weeks
Otherwise you can try to run via the root user
@eladm-ultrawis commented on GitHub (Nov 11, 2023):
@ChristopherHX this happens way before checkout. when setting up vcpkg. also, I think your chown command lacks some parameters (like the user). can you please elaborate?
I tried to run it like so:
and I get
and without it I get:
@ChristopherHX commented on GitHub (Nov 11, 2023):
@eladm-ultrawis
github.actoris never a valid user (usually the Github User Name, the real unix user name is runner/runneradmin for hosted runners). Yeah I forget that user bit in my snippedThis would fail if your cwd is like /path or even /. act doesn't have a
_workfolder your actions assumes to exist.I really meant the
..part two times, otherwise${{ github.workspace }}/../../bwould still be a permission problem...Actually
github.actorin act should even contain a slash, but not my problem.Due to my restricted access level here, it may take some weeks-months even if I created a patch for act.
@ChristopherHX commented on GitHub (Nov 11, 2023):
Without a checkout I'm not even shure you can do..
..in act with rootless users.
Might need to be fixed aswell.
If the actions data needs to be accessed between job and docker actions, act needs more advanced changes
@github-actions[bot] commented on GitHub (May 10, 2024):
Issue is stale and will be closed in 14 days unless there is new activity