Skip to content
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

Closed
1 task done
nikola-jokic opened this issue Jan 24, 2022 · 5 comments · Fixed by #14553
Closed
1 task done

Explanation of using relative paths in an entrypoint causing confusion #14551

nikola-jokic opened this issue Jan 24, 2022 · 5 comments · Fixed by #14553
Labels
content This issue or pull request belongs to the Docs Content team help wanted Anyone is welcome to open a pull request to fix this issue

Comments

@nikola-jokic
Copy link
Contributor

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 entrypoint

As 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

@nikola-jokic nikola-jokic added the content This issue or pull request belongs to the Docs Content team label Jan 24, 2022
@welcome
Copy link

welcome bot commented Jan 24, 2022

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.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jan 24, 2022
@ramyaparimi ramyaparimi added waiting for review Issue/PR is waiting for a writer's review and removed triage Do not begin working on this issue until triaged by the team labels Jan 24, 2022
@ramyaparimi
Copy link
Contributor

@nikola-jokic
Thanks so much for opening an issue! I'll triage this for the team to take a look 👀

@skedwards88
Copy link
Contributor

Thank you for opening this issue! You or anyone else is welcome to open a PR to address this.

@skedwards88 skedwards88 added help wanted Anyone is welcome to open a pull request to fix this issue and removed waiting for review Issue/PR is waiting for a writer's review labels Jan 31, 2022
@skedwards88
Copy link
Contributor

Actually, I see you already have a PR for this issue 😄 I'll go ahead and link the PR.

@skedwards88 skedwards88 linked a pull request Jan 31, 2022 that will close this issue
5 tasks
@Maseeullahz
Copy link

Maseeullahz commented Jan 31, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team help wanted Anyone is welcome to open a pull request to fix this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants
@skedwards88 @ramyaparimi @Maseeullahz @nikola-jokic and others