The Bouncer server's address. --server overrides it. Without either, the first line of ~/.config/bouncer/server is used
BOUNCER_KEY_FILE
The file holding the requester key. --key-file overrides it
BOUNCER_KEY
The requester key itself, used when no key file is given. A file is safer
BOUNCER_CA_FILE
A PEM file of extra CA certificates, trusted for both Bouncer and OpenBao
HTTPS_PROXY, ALL_PROXY, NO_PROXY
Proxy for HTTPS calls and hosts that bypass it. Lower-case names work too. HTTP_PROXY is never used
XDG_CONFIG_HOME
When set, overrides the configuration folder on Linux and Windows. Without it, Linux uses ~/.config; on Windows, the defaults are %LOCALAPPDATA%\bouncer\server and %LOCALAPPDATA%\bouncer\key
SSL_CERT_FILE
Where the system's CA certificates are, if not in the usual places
BOUNCER_UPDATE_FEED
The update feed for bouncer self-update (Linux)
bouncer exec removes BOUNCER_KEY from the child environment. It passes BOUNCER_KEY_FILE on, and the child can still read the key file. Trust the command you run.
The entrypoint uses these defaults unless a value is supplied. compose.yaml sets some of them; change its values through .env where noted.
Variable
Default
Meaning
BOUNCER_CONFIG
/etc/bouncer/bouncer.yaml
The config file inside the container
BOUNCER_LISTEN
127.0.0.1:8080
The address the server listens on. From BOUNCER_PORT in .env
BOUNCER_DB_PASSWORD_FILE
/run/secrets/bouncer-db-password
The database password file
BOUNCER_WAIT_FOR_OPENBAO
empty
Ignored from 0.5.6, and the entrypoint logs that it is. It used to hold the server back until OpenBao was unsealed; the server now starts anyway and answers 503 until OpenBao is ready (When Bouncer is unavailable)