kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

"kb style" docs: decouple URLs from structure

Browse Source 
Signed-off-by: Solomon Hykes <solomon@dagger.io>
This commit is contained in:
Solomon Hykes
2021-07-16 16:37:29 +00:00
committed by Solomon Hykes
parent 5a8f9d3e7c
commit 57754bebb8
21 changed files with 38 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/administrator/1011-operator-manual.md Symbolic link
View File

@@ -0,0 +1 @@
../1011-operator-manual.md

41
docs/administrator/operator.md
View File

@@ -1,41 +0,0 @@
# 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:
```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
```
To use a buildkit daemon running on a remote docker host (be careful to properly secure remotely accessible docker hosts!)
```shell
export BUILDKIT_HOST=docker-container://super-buildkit
export DOCKER_HOST=tcp://my-remote-docker-host:2376
```
## 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.