[docs-scanner] Contradiction about loading multi-platform images in GitHub Actions

[docker-agent]

File: content/manuals/build/ci/github-actions/multi-platform.md

Issue

The documentation contains contradictory information about loading multi-platform images in GitHub Actions. The opening section states:

The default Docker setup for GitHub Actions runners does not support loading multi-platform images to the local image store of the runner after building them.

However, the basic example at the top of the same page shows a workflow that builds and pushes a multi-platform image without any special configuration:

- name: Build and push
  uses: docker/build-push-action@...
  with:
    platforms: linux/amd64,linux/arm64
    push: true
    tags: user/app:latest

This example works fine because it's pushing to a registry, not loading locally. But the page doesn't clarify this distinction until the "Build and load multi-platform images" section, which creates confusion about when the limitation applies.

Why this matters

A reader following the basic example might think they can simply add load: true to get the multi-platform image locally, which will fail. The page structure suggests that multi-platform builds have a fundamental limitation, when the limitation only applies to the specific case of loading to the local image store (not pushing to a registry).

The contradiction is between the general statement about "does not support loading multi-platform images" and the working example that builds multi-platform images successfully (because it pushes rather than loads).

Suggested fix

Clarify the limitation upfront in the opening paragraph:

The default Docker setup for GitHub Actions runners supports building and pushing multi-platform images to registries. However, it does not support loading multi-platform images to the local image store of the runner after building them. To load a multi-platform image locally, you need to enable the containerd image store option for the Docker Engine.

This makes it clear that the limitation is specific to local loading, not to multi-platform builds in general.

---

Found by nightly documentation quality scanner