From 36ac04c1fa060dd075a52898d5efad84371f4989 Mon Sep 17 00:00:00 2001 From: Dan Keder Date: Tue, 20 Dec 2016 00:02:42 +0100 Subject: [PATCH] Add a note to `env_file` option (#932) * Add a note to `env_file` option --- compose/compose-file.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/compose/compose-file.md b/compose/compose-file.md index f0660d0f69..c247b7dd09 100644 --- a/compose/compose-file.md +++ b/compose/compose-file.md @@ -276,7 +276,6 @@ The entrypoint can also be a list, in a manner similar to > clear out any default command on the image - meaning that if there's a `CMD` > instruction in the Dockerfile, it will be ignored. - ### env_file Add environment variables from a file. Can be a single value or a list. @@ -304,6 +303,10 @@ beginning with `#` (i.e. comments) are ignored, as are blank lines. > build. Use the [args](compose-file.md#args) sub-option of `build` to define build-time > environment variables. +The value of `VAL` is used as is and not modified at all. For example if the value is +surrounded by quotes (as is often the case of shell variables), the quotes will be +included in the value passed to Compose. + ### environment Add environment variables. You can use either an array or a dictionary. Any