grafana beyla

The image runs as root and uses the entrypoint /usr/local/bin/beyla. Beyla is configured entirely through environment variables and/or a YAML config file (BEYLA_CONFIG_PATH); it has no subcommands.

$ docker run --rm --privileged --pid=host \
  -e BEYLA_OPEN_PORT=8080 \
  -e BEYLA_TRACE_PRINTER=text \
  registry.ghost-prod.alphabravo.io/ghost-base/beyla:<tag>

This selects the process listening on port 8080 as the instrumentation target and prints captured request traces to standard output.

Common beyla use cases

Print traces for a local service to stdout

The quickest way to confirm Beyla is instrumenting a workload. Beyla selects the target by listening port and prints a span line per captured request, which is useful for validating connectivity before wiring up a backend.

$ docker run --rm --privileged --pid=host \
  -e BEYLA_OPEN_PORT=8080 \
  -e BEYLA_TRACE_PRINTER=text \
  -e BEYLA_SERVICE_NAME=my-service \
  registry.ghost-prod.alphabravo.io/ghost-base/beyla:<tag>

Export OpenTelemetry traces and metrics to a collector

In production Beyla pushes OTLP to a collector or Grafana Alloy. The following Compose file runs Beyla alongside an OpenTelemetry Collector and instruments every process on the host.

services:
  beyla:
    image: registry.ghost-prod.alphabravo.io/ghost-base/beyla:<tag>
    pid: "host"
    privileged: true
    environment:
      BEYLA_OPEN_PORT: "8080"
      BEYLA_SERVICE_NAMESPACE: demo
      OTEL_EXPORTER_OTLP_ENDPOINT: http://otelcol:4317
    depends_on:
      - otelcol
  otelcol:
    image: otel/opentelemetry-collector:latest
    ports:
      - "4317:4317"

Configure Beyla with a YAML config file

For anything beyond a couple of settings, mount a config file and point BEYLA_CONFIG_PATH at it.

$ docker run --rm --privileged --pid=host \
  -v "$(pwd)/beyla-config.yml:/etc/beyla/config.yml:ro" \
  -e BEYLA_CONFIG_PATH=/etc/beyla/config.yml \
  registry.ghost-prod.alphabravo.io/ghost-base/beyla:<tag>

beyla-config.yml:

discovery:
  instrument:
    - open_ports: 8080
trace_printer: text
otel_traces_export:
  endpoint: http://otelcol:4317

Expose Beyla metrics for Prometheus

Beyla can expose an internal Prometheus scrape endpoint instead of (or in addition to) pushing OTLP.

$ docker run --rm --privileged --pid=host -p 9090:9090 \
  -e BEYLA_OPEN_PORT=8080 \
  -e BEYLA_PROMETHEUS_PORT=9090 \
  registry.ghost-prod.alphabravo.io/ghost-base/beyla:<tag>

For advanced setups — Kubernetes DaemonSet deployment, distributed-trace context propagation, network metrics, and language-specific instrumentation — see the Grafana Beyla documentation.

Non-hardened images vs. Ghost hardened images

Like the upstream grafana/beyla image, this image runs as root and requires eBPF privileges (CAP_BPF / CAP_SYS_ADMIN) and a BTF-enabled kernel — these requirements are inherent to eBPF instrumentation, not added by hardening. The entrypoint is /usr/local/bin/beyla; the upstream binary path /beyla remains available as a symlink, so existing commands and Helm charts that exec /beyla keep working.

Image variants

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 your application in production. These images are intended to be used either directly or as the FROM image in the final stage of a multi-stage build. These images typically:

  • Run as a nonroot user
  • Do not include a shell or a package manager
  • Contain only the minimal set of libraries needed to run the app

  Note: Unlike most DHI runtime images, this image runs as root because eBPF instrumentation requires elevated kernel privileges.

• Build-time variants typically include dev in the tag name and are intended for use in the first stage of a multi-stage Dockerfile. These images typically:

  • Run as the root user
  • Include a shell and package manager
  • Are used to build or compile applications

• FIPS 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.

Migrate to a Ghost hardened image

To migrate your application to a Ghost hardened image, you must update your Dockerfile. At minimum, you must update the base image in your existing Dockerfile to a Ghost hardened image. This and a few other common changes are listed in the following table of migration notes.

The following steps outline the general migration process.

1. Find hardened images for your app.

   A hardened image may have several variants. Inspect the image tags and find the image variant that meets your needs.

2. Update the base image in your Dockerfile.

   Update the base image in your application's Dockerfile to the hardened image you found in the previous step. For framework images, this is typically going to be an image tagged as dev because it has the tools needed to install packages and dependencies.

3. For multi-stage Dockerfiles, update the runtime image in your Dockerfile.

   To ensure that your final image is as minimal as possible, you should use a multi-stage build. All stages in your Dockerfile should use a hardened image. While intermediary stages will typically use images tagged as dev, your final runtime stage should use a non-dev image variant.

4. Install additional packages

   Ghost hardened images contain minimal packages in order to reduce the potential attack surface. You may need to install additional packages in your Dockerfile. Inspect the image variants to identify which packages are already installed.

   Only images tagged as dev typically have package managers. You should use a multi-stage Dockerfile to install the packages. Install the packages in the build stage that uses a dev image. Then, if needed, copy any necessary artifacts to the runtime stage that uses a non-dev image.

   For Alpine-based images, you can use apk to install packages. For Debian-based images, you can use apt-get to install packages.

Troubleshooting migration

The following are common issues that you may encounter during migration.

General debugging

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.

Permissions

Most DHI runtime images run as the nonroot user, but this image runs as root because eBPF instrumentation requires elevated kernel privileges. Ensure the container runtime grants the capabilities described under Start a beyla image.

No shell

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.

Entry point

Ghost hardened images may have different entry points than images such as Docker Official Images. Use docker inspect to inspect entry points for Ghost hardened images and update your Dockerfile if necessary.