From d14173ba593cbc237372d978d05e1f7ea0a0ef30 Mon Sep 17 00:00:00 2001 From: Aurelie Vache Date: Fri, 24 May 2024 17:04:40 +0200 Subject: [PATCH] Fix: update docker compose file reference in metadata.md (#20105) --- content/desktop/extensions-sdk/architecture/metadata.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/desktop/extensions-sdk/architecture/metadata.md b/content/desktop/extensions-sdk/architecture/metadata.md index fd21aa8ed5..23798b5238 100644 --- a/content/desktop/extensions-sdk/architecture/metadata.md +++ b/content/desktop/extensions-sdk/architecture/metadata.md @@ -48,7 +48,7 @@ Other UI extension points will be available in the future. ### VM section The `vm` section defines a backend service that runs inside the Desktop VM. It must define either an `image` or a -`composefile` value that specifies what service to run in the Desktop VM. +`docker-compose.yaml` file that specifies what service to run in the Desktop VM. ```json "vm": { @@ -110,4 +110,4 @@ The `host` section defines executables that Docker Desktop copies on the host. `path` specifies the binary path in the image filesystem. Docker Desktop is responsible for copying these files in its own location, and the JavaScript API allows invokes these binaries. -Learn how to [invoke executables](../guides/invoke-host-binaries.md). \ No newline at end of file +Learn how to [invoke executables](../guides/invoke-host-binaries.md).