From 27f79497828ae8a60e85bd471e5b69d7f1c07b3c Mon Sep 17 00:00:00 2001 From: Ulysses Souza Date: Wed, 21 Oct 2020 10:52:11 +0200 Subject: [PATCH] Fix secrets docs on mounts Signed-off-by: Ulysses Souza --- docs/aci-compose-features.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/aci-compose-features.md b/docs/aci-compose-features.md index 8626e9e5c..6879ab540 100644 --- a/docs/aci-compose-features.md +++ b/docs/aci-compose-features.md @@ -126,7 +126,7 @@ Credentials for storage accounts will be automatically fetched at deployment tim ## Secrets Secrets can be defined in compose files, and will need secret files available at deploy time next to the compose file. -The content of the secret file will be made available inside selected containers, under `/run/secrets/`. +The content of the secret file will be made available inside selected containers, by default under `/run/secrets/`. External secrets are not supported with the ACI integration. ```yaml @@ -147,7 +147,7 @@ secrets: file: ./my_secret2.txt ``` -The nginx container will have secret1 mounted as `/run/secrets/mysecret1/mysecret1`, the db container will have secret2 mounted as `/run/secrets/mysecret1/mysecret2` +The nginx container will have secret1 mounted as `/run/secrets/mysecret1`, the db container will have secret2 mounted as `/run/secrets/mysecret2` **Note that file paths are not allowed in the target**