From fdaaf3711d44b3d3302e4f41edeeff63e8a3672b Mon Sep 17 00:00:00 2001 From: aevesdocker Date: Tue, 26 Aug 2025 14:56:05 +0100 Subject: [PATCH] ENGDOCS-2944 --- content/manuals/compose/how-tos/use-secrets.md | 2 +- content/reference/compose-file/build.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/manuals/compose/how-tos/use-secrets.md b/content/manuals/compose/how-tos/use-secrets.md index d2c6352c3be5..72886b135734 100644 --- a/content/manuals/compose/how-tos/use-secrets.md +++ b/content/manuals/compose/how-tos/use-secrets.md @@ -84,7 +84,7 @@ In the advanced example above: - The `secrets` attribute under each service defines the secrets you want to inject into the specific container. - The top-level `secrets` section defines the variables `db_password` and `db_root_password` and provides the `file` that populates their values. -- The deployment of each container means Docker creates a temporary filesystem mount under `/run/secrets/` with their specific values. +- The deployment of each container means Docker creates a bind mount under `/run/secrets/` with their specific values. > [!NOTE] > diff --git a/content/reference/compose-file/build.md b/content/reference/compose-file/build.md index 4ae115b7b56c..e2d9b1ca908a 100644 --- a/content/reference/compose-file/build.md +++ b/content/reference/compose-file/build.md @@ -49,8 +49,8 @@ services: When used to build service images from source, the Compose file creates three Docker images: -* `example/webapp`: A Docker image is built using `webapp` sub-directory, within the Compose file's parent folder, as the Docker build context. Lack of a `Dockerfile` within this folder returns an error. -* `example/database`: A Docker image is built using `backend` sub-directory within the Compose file parent folder. `backend.Dockerfile` file is used to define build steps, this file is searched relative to the context path, which means `..` resolves to the Compose file's parent folder, so `backend.Dockerfile` is a sibling file. +* `example/webapp`: A Docker image is built using `webapp` sub-directory, within the Compose file's folder, as the Docker build context. Lack of a `Dockerfile` within this folder returns an error. +* `example/database`: A Docker image is built using `backend` sub-directory within the Compose file's folder. `backend.Dockerfile` file is used to define build steps, this file is searched relative to the context path, which means `..` resolves to the Compose file's folder, so `backend.Dockerfile` is a sibling file. * A Docker image is built using the `custom` directory with the user's `$HOME` as the Docker context. Compose displays a warning about the non-portable path used to build image. On push, both `example/webapp` and `example/database` Docker images are pushed to the default registry. The `custom` service image is skipped as no `image` attribute is set and Compose displays a warning about this missing attribute. @@ -61,7 +61,7 @@ The `build` subsection defines configuration options that are applied by Compose `build` can be specified either as a string containing a path to the build context or as a detailed structure: Using the string syntax, only the build context can be configured as either: -- A relative path to the Compose file's parent folder. This path must be a directory and must contain a `Dockerfile` +- A relative path to the Compose file's folder. This path must be a directory and must contain a `Dockerfile` ```yml services: