Self-host Envoy Proxy with Levelrail
Cloud native edge and service proxy on the official image. The install form carries envoy.yaml as an editable file, so it starts with a working listener instead of exiting on a missing config.
- Authorenvoyproxy
- LicenceApache-2.0
- Memory128 MiB
- Services1
How to self-host Envoy Proxy
-
Pull the images
One image is pulled on your server.
Show images
envoyproxy/envoy:v1.40.2
-
Create the app
One service starts in a single Compose app, on ports 10000, 9901.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Open the address to see the greeting, then edit the config file setting to add your own listeners, routes and clusters. The admin interface is on port 9901.
Envoy Proxy requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 10000, 9901
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Envoy Proxy. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Envoy Proxy docs page.
Deploy Envoy Proxy your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Envoy Proxy from the CLI
levelrail-cli templates install envoy --name my-envoy Deploy Envoy Proxy with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/envoy/install \
-d '{
"name": "my-envoy"
}' Envoy Proxy configuration
Envoy Proxy services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| envoy | envoyproxy/envoy:v1.40.2 | 10000, 9901 | none |
Envoy Proxy environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 10000, 9901
- Volumes
- none
Envoy Proxy FAQ
How much memory does Envoy Proxy need?
The catalog lists about 128 MiB of memory for Envoy Proxy.
Does Envoy Proxy run on arm64?
For Envoy Proxy, arm64 support is not confirmed; amd64 is unknown.
What licence is Envoy Proxy under?
Envoy Proxy is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Envoy Proxy need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Envoy Proxy use?
Envoy Proxy listens on ports 10000 and 9901 inside the stack.
Can I deploy Envoy Proxy on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Envoy Proxy, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image envoyproxy/envoy:v1.40.2 is what you deploy there.