Mismatched image name between title and code example in reference
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 86/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- docker
- Domain
- documentation
Research direction
Open the Markdown source for the Docker CLI container run reference at the linked documentation location and find the “Join another container’s PID namespace” example. Confirm the heading and code use the same image name, update the incorrect reference, and verify the rendered page shows matching wording.
Written by the indexing model from the issue text.
Description
Is this a docs issue?
- My issue is about the documentation content or website
Type of issue
Information is incorrect
Description
In https://docs.docker.com/reference/cli/docker/container/run/#example-join-another-containers-pid-namespace the title says Redis, but the code example uses nginx:alpine
Location
https://docs.docker.com/reference/cli/docker/container/run
Suggestion
No response
- Dominant language
- Markdown
- Stars
- 4.7k
- Forks
- 8.5k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 116
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Similar issues
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Humanity AI Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
numfocus/project-fundraising#166 ·
-
area:proxy bug security severity:low track:open-source
Difficulty 2/5 1-3 hours Newbie friendliness 70/100