Skip to content

docs: document multi-platform build limitation for Docker driver#25342

Open
mohithshuka wants to merge 11 commits into
docker:mainfrom
mohithshuka:fix/clarify-no-multiplatform-support-25044
Open

docs: document multi-platform build limitation for Docker driver#25342
mohithshuka wants to merge 11 commits into
docker:mainfrom
mohithshuka:fix/clarify-no-multiplatform-support-25044

Conversation

@mohithshuka

Copy link
Copy Markdown
Contributor

What does this PR do?

Adds a Limitations section to the Docker driver page that explicitly
states multi-platform builds are not supported when using the default
Docker driver. Previously, users would only discover this limitation
at runtime via an error message. This change surfaces it in the docs
so users can choose the right driver upfront.

Related issue

Closes #25044

Type of change

  • Documentation only

Preview

Added to content/manuals/build/builders/drivers/docker.md:

Before: No mention of multi-platform limitation
After: Clear Limitations section with links to alternatives
(docker-container driver and containerd image store)

mohithshuka added 10 commits May 15, 2026 16:36
The previous description said 'optimize your repository storage' which
was vague and did not reflect the page's actual content. The manage.md
page is focused on viewing, filtering, and deleting images and image
indexes. Updated the description to accurately reflect this.

Fixes docker#25005
The daemon configuration overview only mentioned two methods (JSON file
and flags) but was missing the environment variables method via systemd.
Added a new section explaining how to use systemd drop-in overrides to
set daemon environment variables.

Fixes docker#25062
Replace shorthand alias 'docker scout env' with the full canonical
command name 'docker scout environment' in the environment integration
overview page, matching the CLI reference and cli.md usage.

Closes docker#25085
The _index.md page mixed 'docker scout env' and 'docker scout environment'
interchangeably. The CLI reference uses 'environment' as the canonical
name, so prose references are updated to match.

Fixes docker#25085
…ct example

Fixes docker#25192

useState was used on line 286 but was missing from the import statement,
causing an error if users follow the tutorial literally.
The React code example was using useState, useEffect, and
createDockerDesktopClient without importing them, which would
cause errors for anyone copy-pasting the snippet.

Fixes docker#25192
…rial

The createDockerDesktopClient() was declared twice - once at module
level (correct) and again inside the App() function (redundant/incorrect).
Removed the duplicate declaration inside the function.

Fixes docker#25192
The Docker driver page did not mention that multi-platform builds
are unsupported, which caused confusion when users encountered
runtime errors. Added a Limitations section that clearly states
this and links to alternatives.

Fixes docker#25044
@mohithshuka mohithshuka requested a review from dvdksn as a code owner June 12, 2026 12:46
Copilot AI review requested due to automatic review settings June 12, 2026 12:46
@netlify

netlify Bot commented Jun 12, 2026

Copy link
Copy Markdown

Deploy Preview for docsdocker failed. Why did it fail? →

Name Link
🔨 Latest commit 686113c
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6a2c03fe5e39e500080de73f

@github-actions github-actions Bot added area/engine Issue affects Docker engine/daemon area/build Relates to Dockerfiles or docker build command area/extensions Relates to Docker Extensions area/scout Relates to Docker Scout labels Jun 12, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Documentation updates across Scout, Extensions SDK, Engine daemon, and Buildx pages to reflect updated CLI behavior, clarify configuration options, and improve guidance.

Changes:

  • Update Docker Scout “environments” docs to use docker scout environment command wording/examples.
  • Adjust Extensions SDK React examples to create a single Docker Desktop client instance outside the component.
  • Expand and refine Engine daemon + Buildx documentation (env var configuration, QEMU guidance, Docker driver limitations).

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 8 comments.

Show a summary per file
File Description
content/manuals/scout/integrations/environment/_index.md Updates Scout environment command references/examples (but introduces duplication/inconsistencies).
content/manuals/extensions/extensions-sdk/guides/invoke-host-binaries.md Updates React example to use module-scoped ddClient (but adds leading blank lines before front matter).
content/manuals/extensions/extensions-sdk/build/backend-extension-tutorial.md Updates tutorial React example to use module-scoped ddClient and correct imports.
content/manuals/engine/daemon/_index.md Adds environment-variable configuration section (but has rendering and correctness issues).
content/manuals/build/building/multi-platform.md Clarifies when manual QEMU installation is needed.
content/manuals/build/builders/drivers/docker.md Adds “Limitations” section for the Docker buildx driver (needs more precise wording).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +1 to 9






---
title: Invoke host binaries
description: Add invocations to host binaries from the frontend with the extension
@@ -52,15 +52,15 @@ To see all of the available environments for an organization, you can use the
`docker scout env` command.

```console
$ docker scout env
$ docker scout environment
Comment on lines +101 to +102
Alternatively, you can Use the `docker scout environment` command to view the images from the terminal.
use the `docker scout environment` command to view the images from the terminal.
Comment on lines 47 to 48
You can use both of these options together as long as you don't specify the same
option both as a flag and in the JSON file. If that happens, the Docker daemon

To set environment variables for the Docker daemon using systemd, create a
drop-in override file:

Comment on lines +111 to +112
[Service]
Environment="DOCKER_OPTS=--debug --tls=true"
Comment on lines +46 to +48
- Multi-platform builds are not supported. To build for multiple platforms,
use the [`docker-container` driver](./docker-container.md) or enable the
[containerd image store](../../../storage/containerd.md).
Comment on lines +42 to +44
## Limitations

The Docker driver has the following limitations:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is only the case when using graph-drivers, which is no longer the default. On currently supported versions of the docker engine (v29.x) the default is to use containerd snapshotters, which provide multi-platform support.

@mohithshuka

Copy link
Copy Markdown
Contributor Author

Thanks for the clarification! I'll update the section to reflect that
multi-platform support depends on the storage driver, and that containerd
snapshotters (default in v29.x+) do support it.

- Moved Limitations section before Further reading
- Corrected multi-platform statement: it depends on the storage
  driver, not a blanket limitation. Containerd snapshotters
  (default in Docker Engine v29.x+) support multi-platform builds,
  while legacy graph-drivers do not.

Based on review feedback from thaJeztah.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/build Relates to Dockerfiles or docker build command area/engine Issue affects Docker engine/daemon area/extensions Relates to Docker Extensions area/scout Relates to Docker Scout

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Page doesn't say it does not support multiplatform

3 participants