kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity
This repository has been archived on 2024-04-08. You can view files and clone it, but cannot push or open issues or pull requests.
a6fb6ab5c1
dagger/docs/administrator/1013-operator-manual.md
rrylee b29cfa1fc3 docs: discard opentracing doc, using opentelemetry 
Signed-off-by: rrylee <rrylee1994@gmail.com>
2022-04-15 21:47:44 +08:00

1.4 KiB
Raw Blame History

slug displayed_sidebar
/1013/operator-manual/ 0.1

Dagger Operator Manual

Custom buildkit setup

Dagger can be configured to use an existing buildkit daemon, running either locally or remotely. This can be done using two environment variables: BUILDKIT_HOST and DOCKER_HOST.

To use a buildkit daemon listening on TCP port 1234 on localhost:

export BUILDKIT_HOST=tcp://localhost:1234

To use a buildkit daemon running in a container named "super-buildkit" on the local docker host:

export BUILDKIT_HOST=docker-container://super-buildkit

To use a buildkit daemon running on a remote docker host (be careful to properly secure remotely accessible docker hosts!)

export BUILDKIT_HOST=docker-container://super-buildkit
export DOCKER_HOST=tcp://my-remote-docker-host:2376

OpenTelemetry Support

Both Dagger and buildkit support opentelemetry. To capture traces to Jaeger, set the OTEL_EXPORTER_JAEGER_ENDPOINT environment variable to the collection address.

A docker-compose file is available to help bootstrap the tracing environment:

docker-compose -f ./dagger-main/tracing.compose.yaml up -d
export BUILDKIT_HOST=docker-container://dagger-buildkitd-jaeger
export OTEL_EXPORTER_JAEGER_ENDPOINT=http://localhost:14268/api/traces

dagger up

You can then go to http://localhost:16686/ in your browser to see the traces.