Merge pull request #3579 from uselagoon/docs/docker-compose-v2

update docker-compose-v2 docs

docs/using-lagoon-the-basics/docker-compose-yml.md

@@ -212,14 +212,36 @@ By default, Lagoon expects that services from custom templates are rolled out vi
 
 You can also overwrite the rollout for just one specific environment. This is done in [`.lagoon.yml`](lagoon-yml.md#environments-name-rollouts).
 
-## BuildKit and Docker Compose v2
+## Docker Compose v2 compatibility
 
-BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.
+!!! bug
+    Note that while using older versions of Docker Compose V2 locally, you may experience some known issues - these have been resolved in later releases (v2.17.3 onwards).
 
-With the release of Lagoon v2.11.0, Lagoon now provides support for BuildKit-based docker-compose builds. To enable BuildKit for your Project or Environment, add `DOCKER_BUILDKIT=1` as a build-time variable.
+The resolution for these errors is usually to update (or [install a later version](https://docs.docker.com/compose/install/) of) the version of Docker Compose you are using, either standalone or by upgrading the version of Docker Desktop you're using.  See the Docker Desktop [release notes](https://docs.docker.com/desktop/release-notes/) for more information
 
-!!! bug
-    Note that while using BuildKit locally, you may experience some known issues.
+``` shell title="Docker Compose output indicating depends_on error"
+Failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization
+
+or
+
+Failed to solve: drupal9-base-cli: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed`
+```
+
+* These are resolved in Docker Compose v2.13.0
+* This message means that your build has tried to access a Docker image that hasn't been built yet. As BuildKit builds in parallel, if you have a Docker image that inherits another one (as we do in Drupal with the CLI).
+* You can also use the [target](https://docs.docker.com/compose/compose-file/build/#target) field inside the build to reconfigure as a multi-stage build
+* If you are already running a newer Docker Compose version, this error may be because you're defaulting to using a docker-container build context with buildx. You should make sure that `docker buildx ls` shows the docker builder as default, not a docker-container based one. Check the docs on docker buildx [here](https://docs.docker.com/engine/reference/commandline/buildx_use/)
+
+``` shell title="Docker Compose output indicating volumes_from error"
+no such service: container:amazeeio-ssh-agent
+```
+
+* This is resolved in Docker Compose v2.17.3
+* This message means that the service that provides SSH access into locally running containers runs outside of your Docker Compose stack and is inaccessible.
+* The section can also be removed from your `docker-compose.yml` file if you don't require SSH access from inside your local environment.
+
+## BuildKit and Lagoon
+
+BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.
 
-* `Failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization`: This message means that your build has tried to access a Docker image that hasn't been built yet. As BuildKit builds in parallel, if you have a Docker image that inherits another one (as we do in Drupal with the CLI). You can use the [target](https://docs.docker.com/compose/compose-file/build/#target) field inside the build to reconfigure as a multi-stage build
-* issues with `volumes_from` in Docker Compose v2 - this service (that provides SSH access into locally running containers) has been deprecated by Docker Compose. The section can be removed from your `docker-compose.yml` file if you don't require SSH access from inside your local environment, or can be worked around on a project-by-project basis - see https://github.com/pygmystack/pygmy/issues/333#issuecomment-1274091375 for more information.
+With the release of Lagoon v2.11.0, Lagoon now provides support for more advanced BuildKit-based docker-compose builds. To enable BuildKit for your Project or Environment, add `DOCKER_BUILDKIT=1` as a build-time variable to your Lagoon project or environment.