From 414e2914f9bb95cbd5933680cad112239b53a53d Mon Sep 17 00:00:00 2001 From: Jeremy Lin Date: Mon, 16 Aug 2021 16:24:03 -0700 Subject: [PATCH] mention that Docker's --env-file does not unquote values --- Configuration-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Configuration-overview.md b/Configuration-overview.md index 1fd4623..3d7671b 100644 --- a/Configuration-overview.md +++ b/Configuration-overview.md @@ -7,7 +7,7 @@ A common source of confusion is enabling the admin page (which creates the `conf Note that config settings under the `Read-Only Config` section of the admin page can only be set via environment variables, so you must restart vaultwarden to make changes to them. If you keep these environment variables in a file named `.env`, you can load them as follows: * With standalone vaultwarden, by putting `.env` in the current working directory. vaultwarden will attempt to load this file on startup. -* With Docker, by using `docker run --env-file ...` (to have Docker load the env file) or `docker run -v /path/to/.env:/.env` (to have vaultwarden load the `.env` file from inside the container). +* With Docker, by using `docker run --env-file ...` (to have Docker load the env file) or `docker run -v /path/to/.env:/.env` (to have vaultwarden load the `.env` file from inside the container). If you use `--env-file`, note that Docker does not unquote values, so make sure to use `key=val` rather than `key="val"` or `key='val'`. * With Docker Compose, by using the [`env_file`](https://docs.docker.com/compose/environment-variables/#the-env_file-configuration-option) directive. ## Configuration options