Fix HotROD Docker command

[jpkrohling]

Signed-off-by: Juraci Paixão Kröhling juraci@kroehling.de

Which problem is this PR solving?

• The HotROD Docker example is missing the all command

Short description of the changes

• Added the all command
• Split the command into more readable lines
• Fixed versions to 1.6
• Changed the Jaeger command to run in the foreground

[codecov]

Codecov Report

Merging #949 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #949   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files         136    136           
  Lines        6322   6322           
=====================================
  Hits         6322   6322

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 933efb3...754e775. Read the comment docs.

[black-adder]

does this mean we need to remember to update this every time we do a major release?

[jpkrohling]

Yes, or add a note before that asking the reader to verify what's the latest version. The alternative is to keep using "latest" and trust that the "latest" build on Docker Hub is compatible with the command (latest == latest build, not latest version)

[black-adder]

latest == latest build, not latest version I think this is the problem, should we call the latest build master instead?

[jpkrohling]

We could, but do we want to point users to use the tip of the branch, instead of a released version?

[yurishkuro]

I'm fine with the fixed version. We can add a link to docker hub and a note for people to check for latest version.

[yurishkuro]

The problem with latest is that Docker may not re-resolve if if the user already run latest previously when it was pointing to a different image / version.