Docs: guides: customizing your buildkit installation
Signed-off-by: Solomon Hykes <solomon@dagger.io>
This commit is contained in:
parent
bddb9b6543
commit
bea61780d2
38
docs/guides/1223-custom-buildkit.md
Normal file
38
docs/guides/1223-custom-buildkit.md
Normal file
@ -0,0 +1,38 @@
|
||||
---
|
||||
slug: /1223/custom-buildkit/
|
||||
---
|
||||
|
||||
# Customizing your Buildkit installation
|
||||
|
||||
## Using a custom buildkit daemon
|
||||
|
||||
Dagger can be configured to use an existing buildkit daemon, running either locally or remotely. This can be done using the environment variable `BUILDKIT_HOST`.
|
||||
|
||||
To use a buildkit daemon listening on TCP port `1234` on localhost:
|
||||
|
||||
```shell
|
||||
export BUILDKIT_HOST=tcp://localhost:1234
|
||||
```
|
||||
|
||||
To use a buildkit daemon running in a container named "super-buildkit" on the local docker host:
|
||||
|
||||
```shell
|
||||
export BUILDKIT_HOST=docker-container://super-buildkit
|
||||
```
|
||||
|
||||
## OpenTracing Support
|
||||
|
||||
Both Dagger and buildkit support opentracing. To capture traces to
|
||||
[Jaeger](https://github.com/jaegertracing/jaeger), set the `JAEGER_TRACE` environment variable to the collection address.
|
||||
|
||||
A `docker-compose` file is available to help bootstrap the tracing environment:
|
||||
|
||||
```shell
|
||||
docker-compose -f ./dagger-main/tracing.compose.yaml up -d
|
||||
export JAEGER_TRACE=localhost:6831
|
||||
export BUILDKIT_HOST=docker-container://dagger-buildkitd-jaeger
|
||||
|
||||
dagger up
|
||||
```
|
||||
|
||||
You can then go to [http://localhost:16686/](http://localhost:16686/) in your browser to see the traces.
|
Reference in New Issue
Block a user