<!--Delete sections as needed -->
## Description
Updated the "Build Docker image" step in the GitHub Actions workflow
example under "Automate DHI scanning in CI/CD with Docker Scout" to
include `--provenance=mode=max`, `--sbom=true`, and `--push` flags.
<!-- 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
<!--Delete sections as needed -->
## Description
refreshes whilst I was in that space
## 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
## Description
In order to better attribute upgrade sources, we are adding two params -
`ref` and `refAction` to the existing pricing url.
The `ref` will be "Docs" and the `refAction` will be the particular docs
page from where the pricing url click is originated.
## Related issues or tickets
https://docker.atlassian.net/browse/GRO-282
## Reviews
@akristen You should see the new url params when hovering over or
clicking any of the updated pricing urls
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Co-authored-by: Alexa Kristensen <81787716+akristen@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
## Summary
Updated Compose production readiness language to use present-tense
framing instead of stale time-relative language.
## Changes
- Replaced "has traditionally been focused on development and testing
workflows, but with each release we're making progress on more
production-oriented features" with present-tense language that
accurately reflects Compose's current production capabilities
- Changed from developer perspective ("we're making progress") to
user-focused language
- Removed suggestion that Compose is still becoming production-ready
Fixes#24343
---
🤖 Generated with [Docker Agent](https://github.com/docker/docker-agent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
## Summary
Fixed inconsistent version reference in Compose history documentation to
mention both v2 and v5.
## Changes
- Updated statement about Compose file format 1 compatibility to
reference both Compose v2 and v5 instead of only v2, making it
consistent with the document's scope
Fixes#24344
---
🤖 Generated with [Docker Agent](https://github.com/docker/docker-agent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
I noticed that building the examples would produce a client with the
default ("Go-http-client/1.1") User-Agent; this is something to look
into (probably should have a saner default), but regardless, it's
good practice to set your own;
- Update examples to show setting the User-Agent
- Use "log.Fatal" instead of "panic"; both exit the binary, but
probably are slightly more readable.
- Use the authconfig.Encode utility, which codifies the canonical
format to encode the JSON, so that users don't have to replicate
the same format.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
<!--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
<!--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
<!--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
Addresses #7462 — the labels page only linked to the Dockerfile LABEL
instruction for adding labels to images. Rewrote the section with
inline examples showing how to add, inspect, and filter labels for
each object type, including the docker build --label flag.
Addresses #22199 — users were confused that the `dockerfile` property
in a Bake target resolves relative to the `context` directory, not the
working directory. Added an explicit note and example to the targets
page.
Context deduplication has been automatic in Bake for a long time.
The section documenting the manual workaround is no longer needed.
Closes#24309
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
## Summary
Fixed broken cross-reference link to company creation documentation in
organization general settings.
## Changes
- Updated link in
`content/manuals/admin/organization/general-settings.md` from broken
relative path `new-company.md` to correct path
`/manuals/admin/company/new-company.md`
Fixes#24299
---
🤖 Generated with [cagent](https://github.com/docker/cagent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
## Summary
Fixed broken anchor link in organization FAQ that pointed to a
non-existent heading in the onboarding documentation.
## Changes
- Updated anchor in `content/manuals/admin/faqs/organization-faqs.md`
from `#step-1-identify-your-docker-users-and-their-docker-accounts` to
`#step-one-identify-your-docker-users` to match the actual heading in
the onboarding guide.
Fixes#24281
---
🤖 Generated with [cagent](https://github.com/docker/cagent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
## Summary
Updated organization FAQ to include complete list of enforce sign-in
benefits.
## Changes
- Added missing benefits to the enforce sign-in FAQ answer: subscription
benefits and activity insights
- Updated security features benefit to include specific examples (IAM
and RAM)
- Aligned FAQ content with the main enforce sign-in documentation
Fixes#24283
---
🤖 Generated with [cagent](https://github.com/docker/cagent)
Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
The "Experimental" status column already indicates these agents are not
production-ready, making the "In development" notes redundant and
time-relative.
Closes#24274
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Replace "Through this partnership, every E2B sandbox" with direct
statement "E2B sandboxes include"
- Change "which comes pre-installed" to "which is pre-installed"
Closes#24266
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The sidebar badge using time-relative "New" text goes stale silently.
The experimental status is already communicated through the content.
Closes#24265
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add AI overview landing page with decision table and relationship overview.
Reframe Gordon as "AI-powered assistant" instead of "AI agent" to avoid
confusion with Docker Agent. Rename sandbox agent page from cagent.md to
docker-agent.md. Add cross-references where products overlap. Fix doubled
"Docker Docker Agent" in agentic AI guide.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
