OpenTelemetry: Outdated Jaeger docker image

Open Beginner friendly
#3,833 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
docker, typescript
Domain
documentation

Research direction

Open the Fresh OpenTelemetry docs at the Jaeger section linked in the issue and find the Docker image and run command. Replace the end-of-life Jaeger v1 image and update the command to match the Jaeger v2 example in the issue. Done when the docs use the new image and publish the listed ports.

Written by the indexing model from the issue text.

Description

The docker image described on the OpenTelemetry docs page for Fresh: https://usefresh.dev/docs/advanced/opentelemetry#jaeger, uses an end-of-life docker image for Jaeger.

jaegertracing/all-in-one:latest -> jaegertracing/all-in-one:1.76.0

Starting this image shows a large banner

*******************************************************************************

🛑  WARNING: End-of-life Notice for Jaeger v1

You are currently running a v1 version of Jaeger, which is deprecated and will
reach end-of-life on December 31st, 2025. This means there will be no further
development, bug fixes, or security patches for v1 after this date.

We strongly recommend migrating to Jaeger v2 for continued support and access
to new features.

For detailed migration instructions, please refer to the official Jaeger
documentation:  https://www.jaegertracing.io/docs/latest/migration/

Tracking issue: https://github.com/jaegertracing/jaeger/issues/6321

🛑  WARNING: End-of-life Notice for Jaeger v1

*******************************************************************************

The new docker image should be cr.jaegertracing.io/jaegertracing/jaeger:latest (cr.jaegertracing.io/jaegertracing/jaeger:2.19.0)
With a slightly different full docker command

docker run --rm --name jaeger \
  -p 16686:16686 \
  -p 4317:4317 \
  -p 4318:4318 \
  -p 5778:5778 \
  -p 9411:9411 \
  cr.jaegertracing.io/jaegertracing/jaeger:latest

Ref: https://www.jaegertracing.io/docs/2.19/getting-started/

Dominant language
TypeScript
Stars
13.8k
Forks
757
Avg merge
3m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from freshframework/fresh

All issues in freshframework/fresh

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.