Repository navigation
Conversation
Fixes docker#26138 The `ddClient.extension.vm.service.get()` example is missing the closing parenthesis for `console.log`, so readers copying it get invalid TypeScript/JavaScript. What changed: - Added the missing `)` in `content/manuals/extensions/extensions-sdk/dev/api/backend.md`. Validation: - `git diff --check` passed. - Local Prettier check not run: dependencies are not installed in this worktree. - Repository validation not run locally: Docker is unavailable. GitHub Actions and the Netlify preview will provide the repository checks.
## Summary - Fix article before HTTP: "a HTTP Basic Authentication" → "an HTTP Basic Authentication". Tiny unsolicited docs grammar fix.
…ker#26144) ## Description `docker desktop kubernetes status` and `docker desktop kubernetes reset-cluster` are implemented in desktop-cli but had no reference page: `data/cli/desktop` was missing their YAML, which is what the reference pages are generated from. Adds both files and lists them in the parent command's `cname`/`clink` (also fixes `clink` pointing at a nonexistent `docker_desktop_engine_images.yaml`). ## Related issues or tickets https://docker.atlassian.net/browse/DDB-567 ## Reviews - [ ] Technical review - [ ] Editorial review
…#26127) draft pr for first sweep to remove screenshots, pending @aevesdocker return. --------- Co-authored-by: Cursor <cursoragent@cursor.com>
## Description Document HTTP method and path rules for local policy. A local network rule can match specific HTTP methods and URL paths on a destination. No org/admin updates in this update. Supersedes docker#26060 without ask policies. | Page | What changed | | --- | --- | | [`concepts.md`](https://deploy-preview-26162--docsdocker.netlify.app/ai/sandboxes/governance/concepts/) | Method, destination, and path syntax, plus how HTTP and network rules combine. Nested under Network rules, since an HTTP rule is a network rule with a method and path. Notes that L7 evaluation needs the sandbox HTTP proxy, so a connection it can't inspect is blocked rather than evaluated | | [`network.md`](https://deploy-preview-26162--docsdocker.netlify.app/ai/sandboxes/governance/access-controls/network/) | Introduces the capability and routes to the local CLI | | [`local.md`](https://deploy-preview-26162--docsdocker.netlify.app/ai/sandboxes/governance/access-controls/local/) | `--method` and `--path` how-to, split out from the existing rule management. Path must be canonical, and each rule takes one path. Troubleshooting entry for a method or path blocked on an allowed host | | [`monitoring.md`](https://deploy-preview-26162--docsdocker.netlify.app/ai/sandboxes/governance/monitor-and-enforce/monitoring/) | `--type http` listing with the method and path columns, and the `(L4)` and `(L7)` labels in the summary | | [`_index.md`](https://deploy-preview-26162--docsdocker.netlify.app/ai/sandboxes/governance/access-controls/) & [`_index.md`](https://deploy-preview-26162--docsdocker.netlify.app/ai/sandboxes/governance/) | Network bullet notes that a local policy rule can match a host, or an HTTP method and path | ## Related issues or tickets ENGDOCS-3373 ## Reviews - [ ] Technical review - [ ] Editorial review - [ ] Product review --------- Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
…26170) Adds a "Known issues" bullet to the 4.92.0 release notes: WSL integration can fail to start with `timed out waiting for ... to be automounted` when `wsl.conf` sets `[automount] root = /`, or after a container bind-mounts a non-drive path under `/mnt`. Ticket: https://docker.atlassian.net/browse/DDB-709 Reports: docker/desktop-feedback#695, docker/desktop-feedback#697
docs: add static Docker Skills guide under /ai/skills
Publish the Docker Agentic Platform documentation as experimental and add one subscription setup flow for Console, cloud CLI, and API/SDK users. The section and its billing-plan page become discoverable, with an Experimental sidebar badge, overview and signup notices, and a Manuals landing-page entry. Add `/agentic-platform/signup/` for account prerequisites, checkout, account-access troubleshooting, and billing. Companion PRs docker#26158 and docker#26168 can replace duplicated activation instructions with `/manuals/agentic-platform/signup.md#activate-cloud-access` and link billing guidance to `#billing`. CLI sign-in, credential setup, and API authentication stay in those guides. Refresh Console guidance for curated and public kits, custom secrets, Antigravity, optional credentials, provisioning, sandbox platforms and lifecycle actions, shell tabs, port access, external MCP clients, and always-applied policies. Document the 64 MiB declared registry-content limit and 256 MiB kit-file limit. Scope private-kit restrictions to Console launches and qualify rollout-dependent controls. CLI tutorials and kit schema documentation remain in separate work. Validation: scoped rumdl and Vale checks passed for all 12 changed Markdown files with no findings. A production Hugo build passed with Git metadata disabled for the worktree. Rendered checks verified discovery in sitemap, metadata and llms-full, search indexing eligibility, experimental marking, signup anchors, and internal link anchors. Live checkout was not exercised. The branch is squashed into one commit for stacking. @netlify /agentic-platform/signup/ Generated by Codex
Add v3 kit documentation for Docker Sandboxes: concepts, usage, authoring, and kit sets. Link to the upstream specification for reference details and retain v2 guidance. Validation: Markdown/style checks, Hugo build, internal links, and example build checks passed. Closes docker/sbx-releases#569 @netlify /ai/sandboxes/customize/
## Description Add an experimental Sandboxes API and SDK section alongside Docker Sandboxes under AI and agents, at `/ai/sandboxes-api/`. Cover installation of `@docker/sandboxes`, browser and PAT authentication, and a TypeScript walkthrough that launches the shell kit, runs a command, and deletes the sandbox. Explain kits and image choices with examples, along with compute sizes, quotas, permissions, resource lifecycle, errors, and retries. Link subscription setup and billing to the shared Docker Agentic Platform guide. Preserve the previous `/ai/sandboxes/api/` URLs with redirects. Uses the shared Docker Agentic Platform documentation merged in docker#26142. Sibling to docker#26158, which introduces CLI-side Cloud Sandboxes documentation. Include 36 SDK cookbook recipes at `/ai/sandboxes-api/cookbook/` and the public REST API reference at `/reference/api/sandboxes/`. Import the generated export from `docker/sbx-api` commit `60d79c1d` (source `1a7f4026`). Overview and installation remain maintained here. The reference uses the shared API renderer from main, with separate operation and schema pages, streaming and WebSocket details, and a downloadable OpenAPI spec. An API reference link appears in the API/SDK sidebar. A pinned manifest and import script provide the basis for later release automation. Examples are optional in the shared renderer; supplied examples still have to pass schema validation. Requests without body examples use a request-body file with instructions to prepare it. The import copies all selected recipes and the OpenAPI specification byte for byte from the corrected upstream export, without patches or link rewrites. The broken naming recipe remains temporarily excluded. This remains a draft pending validation against the published npm SDK. The imported cookbook contains the TypeScript-only guidance, five-minute request deadlines, kit-readiness explanation, active-policy status requirement, and snapshot-deletion and lifetime-renewal restrictions. Validation: scoped Markdown and Vale checks, full Hugo build, rendered navigation, redirects, and internal links, and TypeScript type-checking against the generated public SDK from `docker/sbx-api` commit `68f214b9`. Import validation also covers all 60 REST operations and 188 schema definitions, 1,198 imported-page links and anchors, desktop/mobile rendering, Markdown output, spec delivery, and a repeat import. The shared renderer tests, strict generation for all five APIs (zero diagnostics), full Hugo build, and verification of 453 HTML/Markdown page pairs and API links pass. No live sandbox execution. The corrected export passes strict generation for all five APIs with zero diagnostics, scoped Markdown/Vale lint, a full Hugo build, and verification of 453 HTML/Markdown page pairs and API links. A repeat import produces identical files. The spec update changes examples only; schemas and operations are unchanged. @netlify /ai/sandboxes-api/ Generated by Codex --------- Co-authored-by: Claude <noreply@anthropic.com>
## Description Add cloud Sandboxes documentation for sbx v0.45.0, covering credentials, network policy, lifecycle, environment files, and transfers between local and cloud sandboxes. Document named sandbox reuse and resume, resource sizes and platform selection, custom secrets, move behavior, and local UDP guidance. Link to the canonical Docker Agentic Platform signup, billing, and Console MCP instructions. Keep CLI sign-in, access checks, and cloud credential setup in the Sandboxes guides. This PR also vendors the CLI reference including `sbx move`, and aligns timeout and move guidance with it. Kits v3 and API/SDK documentation are handled separately. Validation: scoped Markdown and Vale checks and a full Hugo build passed. Cloud and Agentic Platform guides passed rendered internal link and anchor checks, including the canonical signup page's discovery. The earlier CLI import verified all 119 vendored files against upstream byte-for-byte and checked 1,083 rendered CLI-reference links and anchors. Behavior was checked against source; live cloud workflows and checkout were not exercised. @netlify /ai/sandboxes/cloud/ Generated by Codex
Fix the main CI REF_NOT_FOUND failure by pointing the Sandboxes API concepts link to the renamed kits-v2.md page. The target matches the v2 artifact format described by the API. Hugo build, Markdown lint, and Vale pass. @netlify /ai/sandboxes-api/concepts/ Generated by Codex
…#26179) The Sandboxes API workflow links to the v2 kit reference, whose general recommendation to use v3 can confuse API readers. Explain that the documented API artifacts use v2, and scope the v3 development recommendation to the `sbx` CLI. Follow-up to docker#26178. Markdown lint and Vale pass for both changed pages. @netlify /ai/sandboxes-api/concepts/ Generated by Codex
Baby step towards cleaning up the sidenav for the ai/agents section. <img width="306" height="304" alt="image" src="https://github.com/user-attachments/assets/57ebd1df-9c7f-4ee8-a84f-a61ffec2cd90" /> Moves “Use AI models in Compose” into Compose → How-tos and MCP Catalog and Toolkit into Docker Desktop → Features and capabilities, removing both entries from the top-level AI and agents sidebar group. Updates internal source links and preserves existing public URLs. Scoped lint and a Hugo build passed; rendered sidebar ancestry, MCP page URLs, and images were checked locally. Generated by Codex
API generation introduced in docker#26048 added roughly five minutes to site builds: median successful main-branch build-workflow duration rose from 4m 05s to 8m 48s across September 3–25. The pre-build command took 4m 41s–4m 53s in each of four jobs on the merge commit. Vendor the generated presentation model in `data/api-reference.json`, mark it as generated, and let Docker, Netlify, and local Hugo builds consume it directly. Keep the existing rendered-output checks. Move generator tests, strict spec validation, and a byte-for-byte regeneration check into `docker buildx bake validate-api-reference`, inheriting the shared Docker base stage. The target uses the pinned Vacuum release binary with Dockerfile ADD checksum verification and archive extraction instead of compiling Vacuum from source. The existing build workflow runs this target alongside the other validation matrix entries. Only this matrix entry is advisory; its failures do not block site builds or deployment. Validated locally with the Docker target, rejection of deliberately stale data, repeatable generation across directories, a production Hugo build and verification of 453 API HTML/Markdown page pairs, workflow syntax checks, and scoped documentation lint. The prebuilt-binary CI check passed in 1m 40s, down from 5m 15s with source compilation. Remote layer-cache settings were subsequently removed; local Go cache mounts remain. Generated by Codex
Sync the Sandboxes release notes with `hack/sbx-release-notes.py`, adding v0.45.1 fixes and the v0.45.0 cloud-support highlight. Scoped Markdown and Vale checks passed. @netlify /ai/sandboxes/release-notes/ Generated by Codex
## Summary Refresh the vendored Sandboxes cookbook and OpenAPI reference from upstream. Removes standalone MCP gateway start/stop documentation, imports upstream authentication and timeout examples, auto-resume readback guidance, and network-policy selector updates, and regenerates the API presentation data. @netlify /ai/sandboxes-api/cookbook/give-a-sandbox-an-mcp-gateway/ Generated by Codex
…#25798) The cache backends overview says the default `docker` driver can use `gha` when the containerd image store is enabled, but the GHA page still said it was unsupported entirely. Matched the wording used for the registry cache backend so the pages agree. Fixes docker#25396 Signed-off-by: Dean Chen <862469039@qq.com>
…r#25800) The cache backends overview says `local` works with the default docker driver when the containerd image store is enabled, but the local backend page never said that. Added the same driver note used on the registry (and GHA) pages. Follow-up to the inconsistency called out in docker#25396. Signed-off-by: Dean Chen <862469039@qq.com>
## Description Adds an important warning to the `daemon.json` remote-access instructions explaining that setting `hosts` this way isn't supported on Docker Desktop for Windows or Docker Desktop for Mac. The same limitation is already documented in the troubleshooting guide; this puts it at the point where readers make the configuration. ## Related issues or tickets Closes docker#26130 ## Validation - `git diff --check` passes. - Local `rumdl` and Docker validation were unavailable in this environment.
## Description Updates the Docker account recovery documentation to resolve a contradictory instruction in the 2FA recovery flow. The previous instructions directed users who had lost both their authenticator application and recovery code to sign in with their username and password before selecting the recovery option. However, completing the sign-in process requires 2FA verification, so users without access to their authenticator or recovery code may be unable to proceed. This change clarifies that the normal sign-in process cannot be completed when the required 2FA verification code is unavailable and directs affected users to the Docker Support form using the primary email address associated with their Docker ID. ## Changes * Clarified the recovery process for users who have lost both their authenticator and recovery code. * Removed the contradictory instruction to sign in before initiating account recovery. * Directed users to Docker Support for further recovery instructions. * Kept the existing 2FA recovery documentation structure and links intact. ## Related Issue Closes docker#26084 ## Reviews * [ ] Technical review * [ ] Editorial review * [ ] Product review
## Summary Extend the Docker Docs launch timeline through September 27 and feature three Docker Sandboxes launches. ## Selected entries - Docker Sandboxes — Run sandboxes on Docker-managed cloud infrastructure (docker#26142, docker#26157, docker#26158, docker#26181) - Docker Sandboxes — Manage cloud sandboxes with the API and TypeScript SDK (docker#26142, docker#26168) - Docker Sandboxes — Compose sandbox environments with kits v3 (docker#26065, docker#26157) ## Curation notes Retained four entries and removed six entries published before the new August 29 window. No retained entry content or sources changed. Docker Desktop 4.92, DHI webhook metadata, API reference migrations, and the Desktop Kubernetes command references did not meet the threshold for a Docker-wide launch highlight. Generated by Codex
## Summary Add the Docker Skills launch omitted from the September curation in docker#26195 and update the featured ranking. ## Selected entries - Docker Skills — Give coding agents guidance with Docker Skills (docker#26169) ## Curation notes Retained all seven existing entries and expired none. The retained Run agents without mounting host files entry remains in the timeline but is no longer featured, keeping the five featured slots for the highest-ranked launches. Generated by Codex
Update the scope note on the OverlayFS storage driver page to clarify that it covers the classic overlay2 driver, and link to containerd image store for the overlayfs snapshotter. Fixes docker#26163 Signed-off-by: jaideepkrishna <jaideepkrishna2008@gmail.com>
The page said the `gha` cache backend defaults to v1 unless $ACTIONS_CACHE_SERVICE_V2 is set. When `version` isn't passed, BuildKit selects v2 if `url_v2` is set, and otherwise infers the version from the `url` string. Buildx forwards an explicitly supplied version but does not add a version attribute based on ACTIONS_CACHE_SERVICE_V2, so a runner that exposes only $ACTIONS_RESULTS_URL can reach v2 without that variable. It also listed `yes` among the values that enable v2 selection. Buildx parses the variable with strconv.ParseBool, which rejects `yes`. The `url` row claimed it is ignored when `version=2`. It is ignored only when `url_v2` is set; with `version=2` and no `url_v2`, `url` is used. Signed-off-by: Sunmin Lee <134378502+sunm2n@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: aevesdocker <allie.sadler@docker.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>
<!--Delete sections as needed --> ## Description Removes stale content and removes two pages (moves content elsewhere in the section) Accuracy checked against the engineering repo ## 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>
Runs freshness tier 1 pass on Support page To do: - Validate info manually - Update - Run freshness tier 2 - Get TW review - Merge --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Tier 1 freshness pass on `content/manuals/platform-release-notes.md`: retitles the page to "Accounts and admin release notes" to match the sidebar section, rewrites the description, keywords, and intro to describe the area as accounts and admin features instead of naming the Admin Console, wraps entries at 80 characters, fixes "Enhance Container Isolation" to "Enhanced Container Isolation" in the 2024-11-18 entry, and retargets two access token links from published URLs to Hugo source paths. Historical entries that mention the Admin Console are unchanged, and no release history was rewritten. --------- Co-authored-by: Cursor <cursoragent@cursor.com>
github-actions
Bot
added
area/release
area/config
area/tests
area/build
area/build-cloud
area/offload
area/compose
area/desktop
area/dhi
area/engine
area/install
area/swarm
area/security
area/get-started
area/guides
area/hub
area/cli
area/api
area/scout
area/billing
area/subscription
area/admin
area/extensions
area/storage
area/accounts
ci
hugo
dependencies
labels
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
--argument behavior for agent defaultssbx kit addas a sandbox restart, not a container recreation docker/docs#25546 from dvdksn/sbx-kit-add-restart-wording--clonemode docker/sbx-releases#354)externalproperty back to compose and add swarm secrets example using compose (docs: Addexternalproperty back to compose and add swarm secrets example using compose docker/docs#25522)windowsfilterdriver documentation (Fix formatting and grammar inwindowsfilterdriver documentation docker/docs#26073)