OpenTelemetry: Outdated Jaeger docker image
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
- 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 freshframework/fresh
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
freshframework/fresh#3920 ·
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
freshframework/fresh#3803 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
freshframework/fresh#3918 · 1 comment · 4 reactions ·
-
Tab title doesn't update to <Head> <title> when navigating to a page with another <title>Possibly taken @1AbdullahButt claimed this 7 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 57/100
freshframework/fresh#3916 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
freshframework/fresh#3911 ·
All issues in freshframework/fresh
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tintinweb/pi-subagents#459 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
danielmiessler/LifeOS#2830 ·
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day