mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #852] Image selection issue when dealing with file system permissions and package selection #518
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#518
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 @aytey on GitHub (Oct 30, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/852
System information
20.10.9-ceact: (discussed below)actversion:act version 0.2.24-31-g83a28d9Expected behaviour
That using either
ghcr.io/catthehacker/ubuntu:act-latestorghcr.io/catthehacker/ubuntu:full-latest, I should be able to make a working directory in the current repo and be able toapt installgcc-11.Actual behaviour
Here's what I experience:
With
ghcr.io/catthehacker/ubuntu:act-latest(a4d332757f9a) and--bind:mkdirworksgcc-11With
ghcr.io/catthehacker/ubuntu:act-latest(a4d332757f9a) and without--bind:mkdirworksgcc-11With
ghcr.io/catthehacker/ubuntu:full-latest(469ca44c2e1c) and--bind:mkdirfailsgcc-11With
ghcr.io/catthehacker/ubuntu:full-latest(469ca44c2e1c) and without--bind:mkdirfailsgcc-11Workflow and/or repository
actoutputI can provide this, but it is pretty boring, it simply reflects what I gave above; that is:
ghcr.io/catthehacker/ubuntu:act-latestallows me to make directories, but doesn't havegcc-11ghcr.io/catthehacker/ubuntu:full-latesthasgcc-11, but doesn't allow me to make directoriesOutput of
act -P ubuntu-latest=ghcr.io/catthehacker/ubuntu:full-latest --bind -v@catthehacker commented on GitHub (Oct 30, 2021):
Already tracked in #398
@aytey commented on GitHub (Oct 30, 2021):
@catthehacker apologies for the duplicate.
How does
ubuntu:act-latestcompare toubuntu:full-latest? Is this documented anywhere?@catthehacker commented on GitHub (Oct 30, 2021):
ubuntu:act-latestusesrootuserubuntu:full-latesthasrunneruser@aytey commented on GitHub (Oct 30, 2021):
Are these two the right way around? I thought that it was the opposite (i.e., that
act-latestusesrunner)?Also, I think there's more to it than that -- the
aptrepos are different between them:gcc-11exists as a package inubuntu:full-latestbut not inubuntu:act-latest.@catthehacker commented on GitHub (Oct 30, 2021):
gcc-11is not available in default repos for Ubuntu 20.04@aytey commented on GitHub (Oct 30, 2021):
Ah, okay, so
full-latestcontains the extra repos that GitHub supplies in their images? Is there a "full-latestincludingrunnerusage" image? It is okay if this is a no, but I just want to check.@catthehacker commented on GitHub (Oct 30, 2021):
@aytey commented on GitHub (Oct 30, 2021):
I'm not trying to be annoying or difficult, but those two images are "quite different" different -- to match what a user might see running under Actions on GitHub, you really need something that is a combination of both of those (at least in my testing).