mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #2132] $XDG_RUNTIME_DIR is set but the directory is not present #1017
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#1017
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 @kortschak on GitHub (Dec 17, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/2132
Bug report info
Command used with act
Describe issue
The
$XDG_RUNTIME_DIRenv var is set, but the directory it points to is not present and cannot be made (the second part as is correct). When a GitHub actions is run, the var is also set, but the runtime dir is available, see here for the same workflow there.The XDG spec says that an application should be prepared to handle cases where the variable is not set and provide an alternative. It does not say that a set var can point to a non-existent directory and handle that case.
The work flow here is a minised reproducer. In the actual work flow the behaviour here breaks the build.
Link to GitHub repository
https://github.com/kortschak/counter_act
Workflow content
Relevant log output
Additional information
No response
@ChristopherHX commented on GitHub (Dec 17, 2023):
Should I remove the XDG_RUNTIME_DIR from the image dump?
Or add it as empty folder?
It's not a bug of act, that image is part of https://github.com/ChristopherHX/runner-image-blobs. E.g. Uploading the VM to ghcr.io and mirror it to the well known tags
@kortschak commented on GitHub (Dec 17, 2023):
@ChristopherHX Thanks. Yeah, either of those options is acceptable.
@ChristopherHX commented on GitHub (Dec 17, 2023):
@kortschak Can you confirm if this issue is fixed by updating the images? (should be updated by default, by running act)
e.g The XDG_RUNTIME_DIR folder should exist as of now.
@kortschak commented on GitHub (Dec 18, 2023):
@ChristopherHX That fixes the behaviour in the reported workflow, and the real workflow shows that the ownership is also correct. Thank you for the rapid fix.