Skip to content

docs: keep Docker Agent Community on GitHub Pages - #26368

Merged
dvdksn merged 4 commits into
docker:mainfrom
aheritier:docs/docker-agent-community-ia
Oct 27, 2026
Merged

dvdksn merged 4 commits into
docker:mainfrom
aheritier:docs/docker-agent-community-ia

Conversation

@aheritier

@aheritier aheritier commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Stop mounting Docker Agent Community on docs.docker.com; keep technical sections and Guides mounted.
  • Sync the module pin and generated vendor files to Docker Agent v1.152.0, which includes docs: add community resources and keep Community on GitHub Pages docker-agent#4618 (cc52bd76).
  • Redirect the Community root, Contributing, and Resources to GitHub Pages. Preserve the three technical-page redirects through upstream aliases.

Merge order

Depends on #26451 for Go 1.27. This branch includes its commit by ancestry; both PRs target main. Merge #26451 first.

Coordinate with the docs team: this supersedes the sync in #25913. Draft #25919 remains suspended and compatible. Neither bot PR was edited or closed.

Redirects

Former /ai/docker-agent/ path Destination
community/ https://docker.github.io/docker-agent/community/contributing/
community/contributing/ https://docker.github.io/docker-agent/community/contributing/
community/resources/ https://docker.github.io/docker-agent/community/resources/
community/telemetry/ /ai/docker-agent/configuration/telemetry/
community/opentelemetry/ /ai/docker-agent/configuration/opentelemetry/
community/troubleshooting/ /ai/docker-agent/guides/troubleshooting/

The GitHub Pages /community/ root returns 404, so the former section root redirects to Contributing.

Validation

CI passes, including build, vendor validation, and redirect tests. Local checks passed for all 9 redirect unit tests, six generated mappings, and 24 CloudFront cases covering trailing slashes and query strings.

@netlify

netlify Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit d80a719
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6adfc7aa2e2ca372bf6a87fd
😎 Deploy Preview https://deploy-preview-26368--docsdocker.netlify.app
📱 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.

@github-actions github-actions Bot added hugo Updates related to hugo area/config labels Oct 16, 2026
@aheritier
aheritier force-pushed the docs/docker-agent-community-ia branch from 055c4f6 to 8fc1a3e Compare October 26, 2026 13:16
@aheritier
aheritier marked this pull request as ready for review October 26, 2026 13:19
Copilot AI balanced review requested due to automatic review settings October 26, 2026 13:19

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.

🟡 Changes recommended

The release/module/vendor sync and validation remain necessary, and the former Community section root needs a redirect.

2 open issues
What changed in this PR

Keeps Docker Agent Community on GitHub Pages while retaining technical documentation and Guides on docs.docker.com.

Changes:

  • Removes the Community Hugo mount.
  • Adds external redirects for Contributing and Resources.
  • Leaves module and vendor pins unchanged pending the coordinated release sync.
File Description
hugo.yaml Removes the Community mount and documents its publishing location.
data/​redirects.yml Redirects two Community pages to GitHub Pages.

Review effort: Balanced

Comment thread hugo.yaml Resolved
Comment thread data/redirects.yml Resolved
Stop mounting Community and redirect its public entry points to GitHub Pages. Leave the release pin and vendor unchanged pending the upstream documentation release.
@aheritier
aheritier force-pushed the docs/docker-agent-community-ia branch from 8fc1a3e to 03398d1 Compare October 26, 2026 16:35
@aheritier
aheritier requested a review from dvdksn as a code owner October 26, 2026 16:35
@github-actions github-actions Bot added area/release Relates to CI or deployment dependencies Vendoring, packaging updates labels Oct 26, 2026
The Community section is no longer mounted on docs.docker.com, and its upstream root returns 404. Send the former root URL to the contributing page alongside the existing page redirect.
dvdksn added a commit that referenced this pull request Oct 27, 2026
Update `GO_VERSION` from 1.26 to 1.27 in the root and releaser
Dockerfiles. Keep the floating minor-version image tags used in
6a09393 and da38930; both 1.27 tags resolve to Go 1.27.3 on
October 26, 2026. Unlike those broader updates, this PR leaves module
files and the Go version used in documentation examples unchanged.

Docker Agent v1.151.0 and later require Go 1.27. The official Go image
sets `GOTOOLCHAIN=local`, so the Go 1.26 build cannot vendor those
releases. Daily `sync-docker-agent-docs` runs have failed since at least
October 24, 2026; the [October 26
run](https://github.com/docker/docs/actions/runs/40261071727) reports
this version mismatch while vendoring v1.152.0.

#26368 will be stacked on this PR to sync Docker Agent v1.152.0 and fix
the Community links. Merge this toolchain upgrade first.

Validation: `dockerfile-lint`, `releaser-build`, `releaser-test` (9
tests), and `validate-api-reference` passed with `docker buildx bake`.
Local `validate-vendor` and `test` hit the existing Community vendor
mismatch and nine missing references from the separately applied #26368
changes. CI on this isolated two-line PR is the authoritative check for
those targets.
@dvdksn
dvdksn merged commit e9c01ea into docker:main Oct 27, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/config area/release Relates to CI or deployment dependencies Vendoring, packaging updates hugo Updates related to hugo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants