Automated crawlers had no dedicated trap route in the docs site. Add a hidden site-wide footer link to a noindex page whose existing Marlin pageview identifies requests.
Co-Authored-By: Codex <codex@openai.com>
The agent guide did not explain how sidebar recursion and sitemap filtering interact for hidden pages and sections.
Document tree construction, discovery exclusions, subtree cascading, and branch-scoped hidden navigation.
Agentic Platform child pages remained visible to generated discovery indexes because only the section root disabled sitemap output.
Cascade the sitemap setting and reveal hidden descendants only within the active sidebar branch.
<!--Delete sections as needed -->
## Description
Added back the attribute `external` in the `/reference/compose/secrets`
section with a warning that this attribute is only available for Docker
Swarm. Additionally, I added a small toy reference example to the
section "Defining and using Secrets in compose files" and moved the
section outside of the "Examples" section. The reason why I did this is
because I noticed the Examples are all runnable steps that showcase
concrete usage of secrets, the example I added is just a
skeleton/reference to how they should be used in conjunction with
`docker secret create...`, not a true able-to-run example like the ones
below. I also changed the hyperlink from
`/reference/compose-file/legacy-versions.md` to
`/reference/compose-file/secrets.md`.
A few caveats that I wasn't sure about when writing this:
- I'm not sure if using the "[!NOTE]" in the attributes list is the
approach maintainers and writers might favor and I can change it
accordingly
- I'd love to hear feedback on moving "Defining and using secrets in
compose files" outside of "Examples" due to my reasoning above
Edit:
I'm also not opposed to making a fully working example using compose,
stack and secrets and putting the section back under `Examples`
<!-- Tell us what you did and why -->
## Related issues or tickets
#25491
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
## Summary
Adds the Docker Agentic Platform plan page and related billing cycle
updates. The page stays published and linkable, but is unlisted from
nav, search, and the plans grid.
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com>
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
## Summary
Remove the scheduled What's New curation workflow and its dedicated
agent configuration. Tune the retained skill for manual use: report
every selected entry explicitly, summarize retained and expired entries,
limit exclusion notes to credible candidates, and avoid
workflow-specific `.pr-body.md` files.
Generated by Codex
Co-authored-by: Claude <noreply@anthropic.com>
build.network was showing `custom_network_1`, which looks like a
user-defined Compose network. it's the RUN networking mode (`default` /
`none` / `host`), same as `docker build --network`.
@netlify /reference/compose-file/build/
Fixes#21982
Signed-off-by: Dean Chen <862469039@qq.com>
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
Signed-off-by: aevesdocker <allie.sadler@docker.com>
The scheduled curation workflow adds operational complexity to an editorial task that requires human review.
Remove the automation and tune the retained skill to report decisions directly without workflow-specific handoff files.
Co-Authored-By: Claude <noreply@anthropic.com>
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Signed-off-by: aevesdocker <allie.sadler@docker.com>
The t3code kit in sbx-kits-contrib installs the build toolchain and the
t3 npm package at sandbox creation, replacing the manual apt-get setup
as the recommended path. Keep the manual install as the fallback for
existing sandboxes.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Clarify that .sbxenv.yaml must stay outside the primary workspace and any additionalWorkspaces mounts, and make the direct-mount warning explicit in the field reference.
Change notes:
- content/manuals/ai/sandboxes/configuration/environment-files.md - clarify that environment files must stay outside every mounted workspace
Align DVP Starter/Growth reports and apply steps with the Hub landing
page and Insights docs, and adjust plan sidebar weights and linkTitles.
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
The general AI ownership rule also covered sandbox governance documentation. Add a narrower rule assigning governance and audit log pages to Craig Osterhout.\n\nCo-Authored-By: Claude <noreply@anthropic.com>
## Summary
Add a Docker Verified Publisher (DVP) plan page covering Starter and
Growth, including apply, tracked companies, and billing. Also list DVP
on the subscription overview and plans index.
Related: https://github.com/docker/docs/pull/25891 (product/program
updates; this PR covers billing and subscription workflows)
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
The kit reference did not state that setup.files runs as the non-root agent user. Document the UID 1000 write restriction and direct root-owned path writes to setup.install.
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
## Description
The sbxenv docs
[document](https://docs.docker.com/ai/sandboxes/sandbox-environments/#workspace)
the direct mount risks, mirroring them here for completeness.
## Related issues or tickets
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [x] Editorial review
- [x] Product review
T3 depends on node-pty, which has no Linux prebuilds, so a sandbox
needs a compiler, make, and python3 for the first connection to
succeed. Adds this as a prerequisite and expands the "server never
becomes ready" troubleshooting section to distinguish a missing
toolchain from a full disk, since both produce the identical error.
Signed-off-by: Manuel de la Peña <manuel.delapena@docker.com>
T3 Code connects to sandboxes over the same SSH integration as VS
Code and Cursor, with no dedicated Docker Sandboxes support on its
side. Adds a Connect page plus a disk-space troubleshooting note for
the "server never became ready" timeout.
Signed-off-by: Manuel de la Peña <manuel.delapena@docker.com>
