## Summary
Clarify that virtual desktop infrastructure environments running `sbx`
must support nested virtualization. The note sits after the platform
prerequisites so it is discoverable without interrupting the standard
setup flow.
@netlify /ai/sandboxes/get-started/
[Preview the updated get-started
page](https://deploy-preview-25723--docsdocker.netlify.app/ai/sandboxes/get-started/)
Generated by Codex
The sandbox prerequisites mentioned nested virtualization only for generic Linux VMs, which could leave VDI users unsure whether the requirement applies. Add a concise VDI-specific nested virtualization requirement after the platform prerequisites.
Document BUILDX_NO_DEFAULT_OCI_ARTIFACT as a compatibility escape hatch for registries that reject OCI artifact attestations.
Add the corresponding Buildx version requirement to the summary bar metadata.
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Image mounts linked to /manuals/dhi/troubleshoot.md, which moved to /manuals/dhi/how-to/troubleshoot.md in #25589 and broke the Hugo build.
Co-authored-by: Cursor <cursoragent@cursor.com>
Registry credential docs still described writing credentials into sandbox config files at creation time.
Update the Sandboxes credentials and workflow pages to describe proxy-based registry authentication and the remaining create-time behavior for global credentials.
## Summary
Clarify that ChatGPT's remote server requires the `codex` command in the
sandbox and that the Codex sandbox template used by the Connect steps
includes it. This preserves the app-specific requirement without
implying that readers must create the sandbox before following the
connection instructions.
@netlify /ai/sandboxes/integrations/chatgpt/
Preview:
https://deploy-preview-25649--docsdocker.netlify.app/ai/sandboxes/integrations/chatgpt/Closes#25648
Generated by Codex
<!--Delete sections as needed -->
## Description
Removed a broken link to the XDG Base Directory Specification. The link
doesn't resolve and users don't need to know the spec. They're just
setting/checking an environment variable.
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Editorial review
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
Noticed the freshness agents seem to prefer ## Next steps over ## What's
next. I like this standard in any case, so updated my docs area to
reflect it. May follow up with team to standardize on the rule
Co-authored-by: Cursor <cursoragent@cursor.com>
<!--Delete sections as needed -->
## Description
- Added changelog attestation.
- Updated the wording to be less authoritative, noting that the actual
attestations for a given image may differ and directing users to Docker
Scout for the full list.
## Related issues or tickets
https://docker.slack.com/archives/C04300R4G5U/p1785235912818699
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Editorial review
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
Consolidate duplicate billing content, fix docs that described an
outdated portal UI, and delete a standalone page (cycle.md) by merging
it into details.md.
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
## Summary
Refreshes the Docker accounts section to clarify what a Docker account
is, how Docker IDs / email / sign-in methods relate, and how individual
accounts differ from organizations. Also updates create, manage,
deactivate, and FAQ pages for terminology consistency, clearer
verification/sign-in flows (tabs), and cross-links.
## Changes
- Expand accounts overview with identity and individual vs organization
concepts
- Restructure create-account and sign-in steps into tabs; tighten
OTP/verification copy
- Refresh manage, deactivate, and FAQ pages (titles, linkTitles,
wording, What's next)
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Greg Mondello <72952982+gmondello@users.noreply.github.com>
The second grep exits after finding the next release heading, which
can close the pipe while the first grep is still writing. With
pipefail, that SIGPIPE is reported as if the requested release notes
were missing.
Read the release file directly with awk and stop at the next level-two
heading so early termination cannot fail an upstream process.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Show the Engine 29.5 opt-in listener and matching client endpoint.
Explain group access and why the socket should use a user-profile
path.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
