mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1659] Runner filesystem can't be written to #823
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#823
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 @pentago on GitHub (Mar 2, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1659
Bug report info
Command used with act
Describe issue
While using action that writes to filesystem (e.g. docker-login-action) the build fails because container filesystem cannot ber written to in case where said action tries to save docker registry creds to a file like
/root/.docker.Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@LaurentLesle commented on GitHub (May 12, 2023):
same issue when I try to login to azure with az login
the home folder is not writable despite showing rwx
@zachroofsec commented on GitHub (Oct 23, 2023):
I was facing this issue as well. For some reason, this error stopped when I disabled the
Use containerd for pulling and storing imagessetting within Docker Desktop. Not sure if this applies to all environments... so your results might vary 👍@github-actions[bot] commented on GitHub (Apr 21, 2024):
Issue is stale and will be closed in 14 days unless there is new activity