tempo query
FIPS 140-3Developer toolsA minimal Grafana Tempo Query (Jaeger storage plugin) image
A minimal Grafana Tempo Query (Jaeger storage plugin) image
Pull the latest version of this image from the Ghost registry. Pulling requires authentication — generate a token and run docker login first (see Authentication below).
The Ghost catalog is public to browse, but pulling images requires an account. Generate a pull token below (or from your Account → Tokens page) — you'll get a ready-to-paste docker login command, then docker pull works.
The username is generated automatically (it looks like robot$<project>+<auto-id>, not the name you typed) and is included in the docker login command above. The secret is shown only once when you create the token.
All Ghost images are signed with cosign. Verifying the signature before deployment ensures the image has not been tampered with.
Install cosign via brew install cosign or download from the Sigstore releases page.
Reference this image in your Dockerfile as a base layer:
This is a vendor-built FIPS-enabled image: its cryptography runs on FIPS 140-3 validated modules configured by the upstream vendor. You can inspect the image metadata:
| Standard | FIPS 140-3 |
| Crypto module | Vendor-configured validated modules |
| Cryptography | Validated modules only |
| Use case | Government, regulated industries, compliance workloads |
All examples in this guide use the public image. If you've mirrored the repository for your own use (for example, to your Docker Hub namespace), update your commands to reference the mirrored image instead of the public one.
For example:
registry.ghost-prod.alphabravo.io/ghost-base/tempo-query:<tag><your-namespace>/dhi-tempo-query:<tag>For the examples, you must first use docker login registry.ghost-prod.alphabravo.io to authenticate to the registry to pull the images.
This Ghost hardened image ships the tempo-query binary (/opt/tempo-query/tempo-query), which speaks the Jaeger
storage plugin gRPC protocol on port 7777 by default and forwards queries to your Tempo HTTP API. Configuration
options are covered in the Grafana Tempo documentation.
The process listens on 0.0.0.0:7777 unless you change it. Point at your Tempo HTTP base URL (for example ). You can pass a YAML config file with or set the same keys via environment variables (Viper-style, e.g. ).
backendhttp://tempo:3200-configBACKEND=http://tempo:3200$ docker run --rm -p 7777:7777 \
-e BACKEND=http://tempo:3200 \
registry.ghost-prod.alphabravo.io/ghost-base/tempo-query:2
See the upstream Tempo configuration reference for TLS, tenant headers, and related settings.
| Feature | DOI (grafana/tempo-query) | DHI (registry.ghost-prod.alphabravo.io/ghost-base/tempo-query) |
|---|---|---|
| User | 10001:10001 (numeric UID) | nonroot (runtime/FIPS) |
| Shell | No | No (runtime/FIPS) |
| Package manager | No | No (runtime/FIPS) |
| Binary path | /tempo-query | /opt/tempo-query/tempo-query |
| Entrypoint | ENTRYPOINT /tempo-query | ENTRYPOINT /opt/tempo-query/tempo-query |
| Default listen addr | 0.0.0.0:7777 | 0.0.0.0:7777 |
| Zero CVE commitment | No | Yes |
| FIPS variant | No | Yes (FIPS + STIG + CIS) |
| Base OS | Distroless (no OS labels) | Ghost hardened images (Debian 13) |
Ghost hardened images come in different variants depending on their intended use. Image variants are identified by their tag.
Runtime variants are designed to run Tempo Query in production. These images typically:
tempo-query binary and TLS certificatescom.docker.dhi.compliance: cis)Dev variants include dev in the tag (for example, 2-dev). They are intended for multi-stage Dockerfiles or
interactive troubleshooting. These images typically:
apt)tempo-query binary as the runtime imageFIPS variants include fips in the variant name and tag. They come in both runtime and build-time variants. These
variants use cryptographic modules that have been validated under FIPS 140, a U.S. government standard for secure
cryptographic operations. For example, usage of MD5 fails in FIPS variants.
To view the image variants and get more information about them, select the Tags tab for this repository, and then select a tag.
For debugging minimal runtime containers without a shell, you can use Docker Debug to attach to running containers.
To migrate your application to a Ghost hardened image, you must update your Dockerfile or Kubernetes manifests. At minimum, you must update the base image in your existing deployment to a Ghost hardened image. This and a few other common changes are listed in the following table of migration notes:
| Item | Migration note |
|---|---|
| Base image | Replace your base images in your Dockerfile or Kubernetes manifests with a Ghost hardened image. |
| Package management | Non-dev images, intended for runtime, don't contain package managers. Use package managers only in images with a dev tag. |
| Non-root user | By default, non-dev images, intended for runtime, run as the nonroot user. Ensure that necessary files and directories are accessible to the nonroot user. |
| Multi-stage build | Utilize images with a dev tag for build stages and non-dev images for runtime. For binary executables, use a static image for runtime. |
| TLS certificates | Ghost hardened images contain standard TLS certificates by default. There is no need to install TLS certificates. |
| Ports | Tempo Query listens on port 7777 by default (above 1024), so no privileged port issues arise. |
| Entry point | Ghost hardened images may have different entry points than upstream images. Inspect entry points for Ghost hardened images and update your deployment if necessary. |
| No shell | By default, non-dev images, intended for runtime, don't contain a shell. Use dev images in build stages to run shell commands and then copy artifacts to the runtime stage. |
The following steps outline the general migration process.
registry.ghost-prod.alphabravo.io/ghost-base/tempo-query with the appropriate tag.backend URL (or equivalent config) is reachable from the Tempo Query
container.The hardened images intended for runtime don't contain a shell nor any tools for debugging. The recommended method for debugging applications built with Ghost hardened images is to use Docker Debug to attach to these containers. Docker Debug provides a shell, common debugging tools, and lets you install other tools in an ephemeral, writable layer that only exists during the debugging session.
By default image variants intended for runtime run as the nonroot user. Ensure that necessary files and directories are accessible to the nonroot user. You may need to copy files to different directories or change permissions so your application running as the nonroot user can access them.
By default, image variants intended for runtime don't contain a shell. Use dev images in build stages to run shell commands and then copy any necessary artifacts into the runtime stage. In addition, use Docker Debug to debug containers with no shell.
Ghost hardened images may have different entry points than upstream Tempo Query images. Use docker inspect to inspect
entry points for Ghost hardened images and update your Kubernetes deployment if necessary.