server command starts a Vault server that responds to API requests. By
default, Vault will start in a "sealed" state. The Vault cluster must be
initialized before use, usually by the
vault operator init command. Each Vault
server must also be unsealed using the
vault operator unseal command or the
API before the server can respond to requests.
For more information, please see:
operator initcommand for information on initializing a Vault server.
operator unsealcommand for information on providing unseal keys.
Vault configuration for the syntax and various configuration options for a Vault server.
Start a server with a configuration file:
$ vault server -config=/etc/vault/config.hcl
Run in "dev" mode with a custom initial root token:
$ vault server -dev -dev-root-token-id="root"
The following flags are available in addition to the standard set of flags included on all commands.
» Command Options
(string: "")- Path to a configuration file or directory of configuration files. This flag can be specified multiple times to load multiple configurations. If the path is a directory, all files which end in .hcl or .json are loaded.
(string: "info")- Log verbosity level. Supported values (in order of detail) are "trace", "debug", "info", "warn", and "err". This can also be specified via the VAULT_LOG_LEVEL environment variable.
» Dev Options
(bool: false)- Enable development mode. In this mode, Vault runs in-memory and starts unsealed. As the name implies, do not run "dev" mode in production.
(string: "127.0.0.1:8200")- Address to bind to in "dev" mode. This can also be specified via the
(string: "")- Initial root token. This only applies when running in "dev" mode. This can also be specified via the
(string: "")- Directory from which plugins are allowed to be loaded. Only applies in "dev" mode, it will automatically register all the plugins in the provided directory.