You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Docker CLI documentation - 2 sets of pages per command is confusing and frustrating #8178
I understand why we have 2 different syntaxes; in Docker Version 1.13 the commands were "revamped" and "improved".
However the 2 sets of documentation pages for the commands is confusing and frustrating.
I being a Docker employee get paid to be frustrated. 😉
Our users, community, customers and partners should not be frustrated.
Example:
If you happen to navigate to the new improveddocker container run command documentation page you cannot see any details or examples for any of the command's options.
For instance show me the syntax and/or an example of coding the --label option.
Zero, nada.
And there is no link or mention to go to the other page -> docker run
If you are lucky enough to find the original/olddocker run command documentation page, all is good as it has more details and examples on the docker run and docker container run command.
For instance the docker run command page has details on the --label option including examples. But this page does not reference the docker container run command page nor mentions it.
The "2 sets" of pages need to be merged together, linked together etc.
Now, there are many other Docker commands (documentation pages) that have this very same issue.
Completely agree with you @gforghetti. I'm working on getting it straightened out, and I'm going to have you in the loop with what I'm working on since you're customer facing. Thanks for your help with this!
@mark-church I wanted to get your thoughts on this issue - as it is relevant to the CLI documentation work that we have to produce soon. We've been aware of the duplicate reference pages issue for some time now, and are hoping to get your input before we go further in reorganizing/refactoring the CLI pages in general.
There hasn't been any activity on this issue for a long time.
If the problem is still relevant, add a comment on this issue.
If not, this issue will be closed in 14 days.
Mark the issue as fresh with a /remove-lifecycle stale comment.
Prevent issues from auto-closing with a /lifecycle frozen comment.
There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.
Prevent issues from auto-closing with a /lifecycle frozen comment.
Activity
ahh-docker commentedon Feb 8, 2019
Completely agree with you @gforghetti. I'm working on getting it straightened out, and I'm going to have you in the loop with what I'm working on since you're customer facing. Thanks for your help with this!
seemethere commentedon Mar 5, 2019
cc @thaJeztah
bermudezmt commentedon Mar 19, 2019
@mark-church I wanted to get your thoughts on this issue - as it is relevant to the CLI documentation work that we have to produce soon. We've been aware of the duplicate reference pages issue for some time now, and are hoping to get your input before we go further in reorganizing/refactoring the CLI pages in general.
docker-robott commentedon Nov 16, 2022
There hasn't been any activity on this issue for a long time.
If the problem is still relevant, add a comment on this issue.
If not, this issue will be closed in 14 days.
Mark the issue as fresh with a
/remove-lifecycle stalecomment.Prevent issues from auto-closing with a
/lifecycle frozencomment./lifecycle stale
thaJeztah commentedon Nov 16, 2022
related: #10471
docker-robott commentedon Feb 14, 2023
There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a
/remove-lifecycle stalecomment.If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.
Prevent issues from auto-closing with a
/lifecycle frozencomment./lifecycle stale
thaJeztah commentedon Feb 14, 2023
/lifecycle frozen
dvdksn commentedon Apr 14, 2026
Closing this as we now only have documentation for the canonical commands, and aliases redirect to the canonical page. No duplication.
eg https://docs.docker.com/reference/cli/docker/container/run/