-
Notifications
You must be signed in to change notification settings - Fork 976
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relative File Paths Are Not Supported by ENTRYPOINT in Docker Actions #1088
Comments
@tahteche can you share some workflow run logs or a link to your workflow run if your repository is public? |
@TingluoHuang Here's the link to the workflow run that failed before I fixed the issue: |
@tahteche thanks. we overwrite the workdir with |
Issue describing the problem: actions/runner#1088
Hi @tahteche, I made a suggestion that is merged to the docs now. Thank you for filing this issue! This also helped us improve the docs so other people don't bump into the same problem. If you have any other suggestions, feel free to comment here, or open another issue. |
On my laptop using relative paths with ENTRYPOINT (exec form) works fine but when I try to run my Docker action in GH Actions I get the following error:
Here's the last stage of the Dockerfile which has the issue:
Using
ls
from within the same working directory to test the exact relative path that failed withENTRYPOINT
showed that the file was in the location I expected.ls -l ./bin/dreamteam
After a couple hours 🙁 I changed the relative path to an absolute one and it worked.
ENTRYPOINT ["./bin/dreamteam"]
->ENTRYPOINT ["/app/bin/dreamteam"]
Like I stated earlier the relative path worked when running Docker locally so I guess this is a bug with GH Actions or at least the difference in behavior should be stated in the documentation for building Docker actions
The text was updated successfully, but these errors were encountered: