## Summary
Gordon's Supplemental Terms are no longer in effect. Replace the
reference under Questions about privacy with a link to the Docker
Subscription Service Agreement.
@netlify /ai/gordon/concepts/data-privacy/
Generated by Codex
Closes#26138
The `get` example under Extensions SDK backend API is missing its
closing parenthesis, so copying it into an extension gives a syntax
error before anything runs:
```typescript
ddClient.extension.vm.service
.get("/some/service")
.then((value: any) => console.log(value)
```
Every other example on the same page closes with `console.log(value));`,
so this matches that rather than only adding the bracket.
## Description
Fix formatting and grammar in the `windowsfilter` storage driver
documentation:
- Code-format the `windowsfilter` driver name for consistency with other
inline code (`size`, `image`, subdirectory names) in the same page
- Fix the double negative "no configuring the windowsfilter storage
driver is not necessary"
- Fix the typo "to for storing"
- Use a space between the number and unit for the default storage limit
(127 GB), per `STYLE.md`
## Related issues or tickets
None.
## Reviews
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
## Summary
**Problem:** Mermaid diagrams briefly showed their raw source before the
SVG appeared, stayed on the wrong palette after a light/dark theme
toggle, and could leave Mermaid's error graphic in the page when a
diagram failed to parse.
**Why this change:** Diagrams are used more often in the docs, so the
renderer needs to match the site theme and avoid flashing source text
while SVGs load.
**Solution:** Replace `mermaid.run()` with a controlled
`mermaid.render()` loop that caches each block's source, skips stale
async results, re-renders when the `<html>` dark class changes,
suppresses Mermaid's default error SVG, and hides `pre.mermaid` until an
SVG is present (or a render error sets `data-error` so the source can
still be inspected).
@netlify /get-started/docker-concepts/the-basics/what-is-a-registry/
Preview:
https://deploy-preview-26304--docsdocker.netlify.app/get-started/docker-concepts/the-basics/what-is-a-registry/
Example of pre-fix behavior:
https://deploy-preview-26283--docsdocker.netlify.app/accounts/organization/
Generated by Cursor
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Monitoring guides were grouped under CI/CD, and several other guides had
categories that did not match their main purpose. Add Observability,
rename Deployment to Services & infrastructure, and move LocalStack and
Django into Testing and Languages & frameworks.
Remove the E2B workflow and integration documentation and both Ollama
application guides. Remove E2B navigation and promotional links.
Redirect former E2B URLs to Docker Sandboxes and former Ollama guide URLs
to Docker Model Runner.
The Build Cloud, Compose, Scout, Testcontainers Cloud, and
container-supported development guides mostly repeat product benefits
and introduce videos instead of teaching distinct tasks.
Remove these five guides and their unused images, update incoming links,
and redirect all former page and chapter URLs to the relevant product
docs or hands-on lab. Keep both administration guides.
The Testcontainers collection includes nine specialized Java integration
tutorials with modest readership and overlapping framework setup.
Remove these guides and their links from the Testcontainers overview,
retaining eleven guides covering language introductions, general
techniques, representative web frameworks, and Testcontainers Cloud.
The NLP examples, TensorFlow.js face detection guide, Neo4j RAG guide,
and video chatbot guide have low readership and repeat application
setup or containerization covered by other guides.
Remove these eight guides and the nine images used only by them.
No remaining content or config entries reference the removed guides.
With the nydus, overlaybd, soci, or stargz snapshotter, docker pull
skips the content of layers that the snapshotter provides. If that
content isn't already stored locally, docker save fails for the image,
and docker push can fail too.
Add a "Lazy pulling" section that explains this default, which layers
it skips, and its limits. It notes that the default needs no
configuration, and that setting the lazy-pull feature overrides it.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
## Description
Add Offload shortcuts for the product page, billing catalog, and
documentation:
- `/go/offload` redirects to
https://www.docker.com/products/docker-offload/.
- `/go/get-offload` redirects to https://app.docker.com/billing/catalog.
- `/go/cloud-flag/` redirects to https://docs.docker.com/offload/.
## Related issues or tickets
DCL-2119
## Reviews
Validated with all nine existing redirect-handler tests and `git diff
--check`. All three shortcuts accept URLs with or without a trailing
slash. The product and documentation pages return HTTP 200; the billing
catalog redirects unauthenticated visitors to login with the catalog as
the return destination.
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
The API reference banner kept its light background when links switched to light colors in dark mode. Add dark background, border, and text colors matching the note callout palette.
## Description
Documents the user-facing changes in Docker Sandboxes v0.47.0 and
updates the CLI reference.
- `sbx run --rm` removes the sandbox when the agent exits, for local and
cloud sandboxes.
- `sbx run --detached` keeps a local sandbox running after its sessions
end.
- Kits can declare the `long-running@1` capability to keep their sandbox
running.
- `sbx move` to the cloud applies the kit's network rules.
- MCP authorization requests `offline_access` with default scopes, so
servers can issue refresh tokens.
- UDP to local-network destinations is blocked regardless of network
policy.
- `sbx --cloud ttl` reports stopped sandboxes as stopped instead of
expired.
- The CLI reference is updated for v0.47.0.
@netlify /ai/sandboxes/usage/
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Doc that adds some context about JIT vs SCIM, per SME resources. Makes
updates to overview docs, troubleshooting, and FAQs. Also includes a
freshness pass from tier 1 and tier 2 review agents.
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
## Summary
Late September accounts and admin changes were missing from the release
notes. Add the Agentic Platform checkout skip, the team page after
create, the member CSV Licenses column, and the support form Legal
topics.
Co-authored-by: Cursor <cursoragent@cursor.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>
sbx --cloud ttl no longer reports a stopped sandbox as expired. Explain
that resuming starts a new time-to-live period and describe the
stopped and ttl_paused JSON fields.
Source: docker/sandboxes#6388
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
UDP to multicast, link-local, unspecified, and broadcast destinations
is dropped before policy evaluation, so no allow rule can permit it.
Explain the effect on discovery protocols and how the network log
reports these connections.
Source: docker/sandboxes#5875
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
When sbx uses recorded default or resource-required scopes, it also
requests offline_access if the authorization server advertises it, so
the server can issue a refresh token. Explicit --scope values are
requested as given.
Source: docker/sandboxes#6284
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
sbx move --to cloud now applies the sandbox's kit or agent network
rules, as sbx --cloud create does. Rules added locally still don't
transfer. Correct the move and cloud network policy pages, which said
no local rules apply.
Source: docker/sandboxes#6707 (backported as #6814)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Explain how a kit declares long-running@1 to keep its sandbox running
after sessions end, how required and optional entries behave, and that
cloud sandboxes and sbx kit add can't provide it.
Source: docker/sandboxes#6710
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Explain that sbx run --detached keeps a local sandbox running after its
sessions end, and that running it against an existing sandbox switches
that sandbox to detached mode permanently.
Source: docker/sandboxes#6600
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Explain that --rm removes a local or cloud sandbox when the agent
session exits, when a reattached sandbox is kept, and why --rm can't be
combined with --detached or --detach-keys.
Source: docker/sandboxes#6601
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
<!--Delete sections as needed -->
## Description
See commit message(s).
Just fixes a small hiccup on the docs! It makes it sounds like Debian
comes with ufw but it doesn't.
> nftables is the default and recommended firewalling framework in
Debian…
>
> It is recommended to run
[?](https://wiki.debian.org/firewalld)firewalld…
>
> \- [Debian Wiki: nftables](https://wiki.debian.org/nftables)
Just to confirm, I also installed Debian on a VM and checked if ufw was
present, and indeed it wasn't. This was run on a fresh express Debian
install:
```txt
root@debian13-uni:/home/seth# ufw
bash: ufw: command not found
root@debian13-uni:/home/seth#
```
- [ ] Technical review
- [x] Editorial review
- [ ] Product review