docker: simplify examples

[MasterOdin]

• The page is in the correct platform folder (common/, linux/, etc.)
• The page has 8 or fewer examples.
• The PR title conforms to the recommended templates.
• The page follows the content guidelines.

This is the first of PRs that is attached to the raised issue #2592, reverting the changes of #1505 to the more common real-world suggested usage, with the intent to create further docker command specific pages.

I'm not sure how you'd want to handle the fact that it has 9 examples though. You could probably merge the two run examples, but not sure how to specify an optional {{command}} parameter.

[sbrl]

Was this meant to be ls instead of ps?

[MasterOdin]

Nope, that's the actual command. I assume it's one of the many reasons why they did the CLI restructure, adding in the newer sub-commands like container, image, etc.

[sbrl]

I see. If the container commands are newer, why are we changing the page to the older commands? I'm confused.

[owenvoke]

@sbrl, see #2592. Looks like the short commands were going to be removed, but then most people tend to use the short commands. It looks like @MasterOdin was thinking of using additional pages for the long commands. So docker-container, etc.

[sbrl]

Ah, I see. This change is ok then :-)

Maybe once those pages are done we can revisit and add a See also.

[MasterOdin]

Yeah, it's kind of a weird spot Docker is in. They added a bunch of sub-commands (container, image, etc.) to allow adding a lot more commands for those specific actions, but left the top level largely alone. As such, while all of the top level commands do have an equivalent action within a sub-command, most docs and things really just use these handful of key top level commands still.

[agnivade]

@MasterOdin - Could you remove one example from the page so that we are under our budget of 8 ?

[stale]

Hi all! This thread has not had any recent activity. Are there any updates? Thanks!

[MasterOdin]

Removed a 9th example from the file, but I'm a bit conflicted. Would it be appropriate to add a {{command}} to the end of the docker run example and reword it to be "Start a container from an image with a custom name and run the command (leave off to use default Dockerfile command)" or something like that or just leave it as is?

[sbrl]

Is the command mandatory, @MasterOdin? Is it the most common use case?

[MasterOdin]

It's not mandatory and if not included, a default command will be executed by the developer of the Dockerfile. The most common usecase would be to not include the command though.

[sbrl]

Perhaps we should leave it off then. If it isn't commonly used, then I think it's better left to a more in-depth guide or tutorial :-)