Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add section for running Envoy via CLI #21811

Merged
merged 5 commits into from
Jul 1, 2022
Merged
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions bazel/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -270,6 +270,16 @@ for how to update or override dependencies.
1. `bazel build envoy` from the Envoy source directory. Add `-c opt` for an optimized release build or
`-c dbg` for an unoptimized, fully instrumented debugging build.

## Running the built Envoy binary on the host system

After Envoy is built, it can be executed via CLI.
phlax marked this conversation as resolved.
Show resolved Hide resolved

For example, if Envoy was built using the `bazel build -c opt //source/exe:envoy-static` command, then it can be executed from the project's root directory by running:
phlax marked this conversation as resolved.
Show resolved Hide resolved

```console
$(bazel info bazel-genfiles)/source/exe/envoy-static --config-path /path/to/your/envoy/config.yaml
```

## Building Envoy with the CI Docker image

Envoy can also be built with the Docker image used for CI, by installing Docker and executing the following.
Expand Down