You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What part(s) of the article would you like to see updated?
When using a custom image, I've observed that GH Actions appears to be setting the container's work directory to its own custom directory. In my case it's __w/server/server. Therefore, any bash command I would've ran as-is successfully fails until I set the working-directory option to the correct value.
I don't know exactly how that value is being set, though it certainly appears to align with the volume paths captured here.
Additional information
I can confirm that setting the working-directory fixed my problem, but I don't know what's causing the issue and therefore what conditions it presents itself in.
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
Sharra-writes
added
needs SME
This proposal needs review from a subject matter expert
and removed
triage
Do not begin working on this issue until triaged by the team
labels
Mar 21, 2025
@richseviora Thank you for opening this issue! I'll get this triaged for review. ✨ Our team will provide feedback regarding best next steps. Thanks for your patience!
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/writing-workflows/choosing-where-your-workflow-runs/running-jobs-in-a-container
What part(s) of the article would you like to see updated?
When using a custom image, I've observed that GH Actions appears to be setting the container's work directory to its own custom directory. In my case it's
__w/server/server
. Therefore, any bash command I would've ran as-is successfully fails until I set theworking-directory
option to the correct value.I don't know exactly how that value is being set, though it certainly appears to align with the volume paths captured here.
Additional information
I can confirm that setting the
working-directory
fixed my problem, but I don't know what's causing the issue and therefore what conditions it presents itself in.The text was updated successfully, but these errors were encountered: