Skip to content

docs: align Build Cloud with standard Buildx - #25885

Draft
dvdksn wants to merge 5 commits into
docker:mainfrom
dvdksn:codex/build-cloud-oss-buildx-docs
Draft

docs: align Build Cloud with standard Buildx#25885
dvdksn wants to merge 5 commits into
docker:mainfrom
dvdksn:codex/build-cloud-oss-buildx-docs

Conversation

@dvdksn

@dvdksn dvdksn commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Summary

Align Docker Build Cloud documentation with the cloud driver in standard Buildx. This removes special Buildx and Compose package installation steps, updates CI guidance to use compatible bundled versions, and integrates cloud builders and output behavior into the Build documentation.

@netlify /build-cloud/setup/

Assumptions and TODOs

  • Buildx v0.37.0 is the minimum standard Buildx release that includes the cloud driver.
  • CI runners with Buildx v0.37.0 or later don't need a separate Buildx installation; the docs retain a manual-install fallback for older runners.
  • Docker Compose uses the installed Buildx plugin, so Docker Build Cloud doesn't require a separate minimum Compose version.
  • Private resource access still requires the private Buildx client; the builder settings documentation retains that compatibility guidance.
  • docker/setup-buildx-action will support the standard Buildx release. An internal TODO tracks whether the docs need to specify a minimum action version.

Related

Generated by Codex

Docker Build Cloud documentation still required private Buildx and Compose packages and repeated those installation steps across CI examples. Document the public cloud driver in Buildx 0.37.0, use compatible packaged Buildx versions, and integrate cloud builders and output behavior into the Build documentation.\n\nCo-Authored-By: Claude <noreply@anthropic.com>
@github-actions github-actions Bot added area/build Relates to Dockerfiles or docker build command area/build-cloud labels Aug 18, 2026
@netlify

netlify Bot commented Aug 18, 2026

Copy link
Copy Markdown

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit a2931b1
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6a8d5f9414a4570008a79383
😎 Deploy Preview https://deploy-preview-25885--docsdocker.netlify.app/build-cloud/setup/
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@dvdksn dvdksn added the status/upstream Problem lives in vendored content; needs fix in the source repo label Aug 18, 2026
dvdksn and others added 3 commits August 25, 2026 08:26
Standard Buildx 0.37 omits private resource access even though the setup draft implied that all Build Cloud users could migrate. Add setup and feature-specific notices directing affected users to remain on the latest private client.

Co-Authored-By: Claude <noreply@anthropic.com>
The setup page should describe the standard Buildx migration without a feature-specific exception. Keep the private Buildx requirement only on the canonical private resource access section.

Co-Authored-By: Claude <noreply@anthropic.com>
Docker Compose uses the installed Buildx plugin for Docker Build Cloud, so it does not need a separate compatibility version. Remove the Compose release TODO and make Buildx 0.37.0 the only version requirement.

Co-Authored-By: Claude <noreply@anthropic.com>
@dvdksn dvdksn added this to the buildx/v0.37.0 milestone Aug 25, 2026
CI runner images can bundle a Buildx plugin older than the Docker CLI installation suggests. Promote the Buildx 0.37.0 prerequisite to an Important callout with a version check and installation fallback.

Co-Authored-By: Claude <noreply@anthropic.com>
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/build-cloud status/upstream Problem lives in vendored content; needs fix in the source repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant