docs: migrate Docker instructions to relative bind mount #374
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
The README > Run using Docker command example
docker run -v ${PWD}:/tmp:ro --rm -i ghcr.io/tcort/markdown-link-check:stable /tmp/README.md
uses
PWD
(Print Working Directory). The syntax${PWD}
can now be replaced by a simpler one using relative paths.Relative paths
The Docker documentation for
docker container run
(with aliasdocker run
) describes the option Mount volume (-v) using relative paths:Change
Use the relative path
.
syntax instead of${PWD}
:Verification
Under Ubuntu
24.04.1
LTSgit clone https://github.com/tcort/markdown-link-check cd markdown-link-check docker run -v .:/tmp:ro --rm -i ghcr.io/tcort/markdown-link-check:stable /tmp/README.md
Confirm that
markdown-link-check
runs successfully.