-
Notifications
You must be signed in to change notification settings - Fork 60.3k
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
Explanation of using relative paths in an entrypoint causing confusion #14551
Comments
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. |
@nikola-jokic |
Thank you for opening this issue! You or anyone else is welcome to open a PR to address this. |
Actually, I see you already have a PR for this issue 😄 I'll go ahead and link the PR. |
Hi I want Make Website But in afghanistan All bank account blocked Could u help me to Make for me Free website?
King_Mlz
… On Feb 1, 2022, at 12:37 AM, Sarah Edwards ***@***.***> wrote:
Actually, I see you already have a PR for this issue 😄 I'll go ahead and link the PR.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
Code of Conduct
What article on docs.github.com is affected?
Dockerfile support
What part(s) of the article would you like to see updated?
ENTRYPOINT
Due to an issue filed at actions/runner #1088, I am filing the issue to resolve confusion about the
workdir
in an entrypointAs the issue stated, documentation should be updated to reduce the confusion when using ENTRYPOINT with the relative path.
There should be a clear explanation about using absolute path if you are using
WORKDIR
inside the Dockerfile, and how to use it with the workdir override--workdir /github/workspace
Additional information
No response
The text was updated successfully, but these errors were encountered: