Tempo is a distributed tracing backend by Grafana.
10K+
ubuntu/tempo is a rock for tempo maintained by Canonical.
Tempo is a distributed tracing backend by Grafana, supporting Jaeger, Zipkin, and OpenTelemetry protocols.
NOTE: These tags follow a specific naming convention that respects the concept of channels.
| Tags | Supported until | Version | Base | Architectures | |
|---|---|---|---|---|---|
2.10-26.04_stable | aliases2-26.04, 2-26.04_beta, 2-26.04_candidate, 2-26.04_edge, 2-26.04_stable, 2.10-26.04, 2.10-26.04_beta, 2.10-26.04_candidate, 2.10-26.04_edge | 08/2026 | 2.10 | 26.04 | amd64 |
| Tags | Support ended on | Upgrade Path | |
|---|---|---|---|
2.7.1-24.04_stable | aliases2.7-24.042.7-24.04_beta2.7-24.04_candidate2.7-24.04_edge2.7-24.04_stable2.7.1-24.042.7.1-24.04_beta2.7.1-24.04_candidate2.7.1-24.04_edge | 05/2025 | - |
2.9-24.04_stable | aliases2.9-24.042.9-24.04_beta2.9-24.04_candidate2.9-24.04_edge | 02/2026 | - |
2.6.1-24.04_stable | aliases2.6-24.042.6-24.04_beta2.6-24.04_candidate2.6-24.04_edge2.6-24.04_stable2.6.1-24.042.6.1-24.04_beta2.6.1-24.04_candidate2.6.1-24.04_edge | 03/2025 | - |
2.10-24.04_stable | aliases2-24.042-24.04_beta2-24.04_candidate2-24.04_edge2-24.04_stable2.10-24.042.10-24.04_beta2.10-24.04_candidate2.10-24.04_edge | 05/2026 | - |
2.8-24.04_stable | aliases2.8-24.042.8-24.04_beta2.8-24.04_candidate2.8-24.04_edge | 11/2025 | - |
2.4.2-22.04_stable | aliases2.4-22.042.4-22.04_beta2.4-22.04_candidate2.4-22.04_edge2.4-22.04_stable2.4.2-22.042.4.2-22.04_beta2.4.2-22.04_candidate2.4.2-22.04_edge | 05/2025 | - |
2.6.1-22.04_stable | aliases2-22.042-22.04_beta2-22.04_candidate2-22.04_edge2-22.04_stable2.6-22.042.6-22.04_beta2.6-22.04_candidate2.6-22.04_edge2.6-22.04_stable2.6.1-22.042.6.1-22.04_beta2.6.1-22.04_candidate2.6.1-22.04_edge | 01/2025 | - |
2.4.0-22.04_stable | aliases2.4.0-22.042.4.0-22.04_beta2.4.0-22.04_candidate2.4.0-22.04_edge | 05/2025 | - |
This rock's entrypoint is Pebble, a container-optimized init process that enables the orchestration of a collection of local service processes as an organized set.
To view the Pebble services and checks defined in this rock:
docker run --rm ubuntu/tempo:2.7.1-24.04_stable plan
To run this rock, use any of the usual container runtimes, for example, docker:
docker run --name tempo-container \
-p 3200:3200 -p 14268:14268 -p 9095:9095 -p 4317:4317 -p 4318:4318 -p 9411:9411 \
ubuntu/tempo:2.7.1-24.04_stable
Access the Tempo API at http://localhost:3200.
Ingestion endpoints for each format open separate ports.
To view the logs of the running container, run:
docker exec tempo-container pebble logs
Or, for a specific service:
docker exec tempo-container pebble logs <service>
Rocks may have predefined health checks that you can list by running:
docker exec tempo-container pebble checks
The overall health of your container can be inspected via:
docker exec tempo-container pebble health
| Option | Description | Default |
|---|---|---|
| TZ | Timezone. | UTC |
| Option | Description | Default |
|---|---|---|
-p <port>:3200 | Expose the container's port 3200 on the host's <port> for the Tempo HTTP API. | None |
-p <port>:9095 | Expose the container's port 9095 on the host's <port> for the Tempo GRPC API. | None |
-p <port>:14268 | Expose the container's port 14268 on the host's <port> for Jaeger thrift format ingestion. | None |
-p <port>:4317 | Expose the container's port 4317 on the host's <port> for OpenTelemetry GRPC ingestion. | None |
-p <port>:4318 | Expose the container's port 4318 on the host's <port> for OpenTelemetry HTTP ingestion. | None |
-p <port>:9411 | Expose the container's port 9411 on the host's <port> for Zipkin format ingestion. | None |
Canonical is the provider of this container image. It is the user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within, as well as with Canonical’s IP Policy.
Content type
Image
Digest
sha256:476b7e6d3…
Size
102.8 MB
Last updated
3 months ago
docker pull ubuntu/tempo:2.10-26.04_stablePulls:
372
Last week