## 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
## Summary
Prototypes a task-first Get started experience organized around three
short journeys:
- Containerization: run a container and application stack, build an
image, and share it.
- AI development: move an existing full-autonomy coding-agent workflow
into a disposable Docker Sandbox.
- Administration: invite a pilot user, apply a Docker Desktop policy,
and verify the managed experience.
The change replaces the existing Get started landing content with a
compact journey selector, adds direct installation paths for Docker and
Docker Sandboxes above the tutorials, adds the tutorials as a
collapsible sidebar group, and updates homepage and `llms.txt` discovery
paths. The container and sandbox tutorials include focused next steps
into relevant concept and manual pages.
The superseded Introduction series and its unused images are removed.
Its published routes and legacy aliases, including the workshop routes
consolidated on `main`, redirect to the replacement container tutorial
or the Get Docker page. Inbound documentation links point to the new
tutorial.
The existing Docker concepts content remains available while this
direction is evaluated.
@netlify /get-started/
## Deploy preview
- [Get started landing
page](https://deploy-preview-25986--docsdocker.netlify.app/get-started/)
- [Containerization
tutorial](https://deploy-preview-25986--docsdocker.netlify.app/get-started/tutorials/run-an-app/)
- [AI agent
tutorial](https://deploy-preview-25986--docsdocker.netlify.app/get-started/tutorials/run-an-agent/)
- [Administrator
tutorial](https://deploy-preview-25986--docsdocker.netlify.app/get-started/tutorials/admin-set-up/)
Generated by Codex
---------
Co-authored-by: Codex <noreply@openai.com>
While reading this page, I noticed "1)" renders as a bullet point while
"2)" stays inline mid-sentence:
> This was made possible because
> 1. the processes running in each container are watching and responding
to
> file changes and 2) the files in your local project directory are
shared
> ...
Checked the file history with `git log -L` — the original text used `1)`
and `2)` symmetrically as an inline parenthetical enumeration, all on
one line. A later commit addressing #24394 (clarifying where the files
are located) expanded the paragraph and reflowed it across multiple
lines, which put `1)` at the start of a line. Per the [CommonMark
spec](https://spec.commonmark.org/0.31.2/#ordered-list-marker), both `.`
and `)` after a digit at the start of a line are valid ordered-list
markers — so `1)` now renders as an actual list item, while `2)`, still
mid-line, stays as plain text. Inconsistent and presumably unintended.
This PR restores the sentence to a single paragraph (matching the
pre-#24394 formatting), keeping the additional clarifying text that
#24394 added. Verified in a local Markdown preview that it now renders
as plain prose with no stray list item.
Get-started publishing page only covered host:container. Add the optional
bind address form and a Compose example so 127.0.0.1:… style mappings are
discoverable.
Fixes#22253
Signed-off-by: Dean Chen <862469039@qq.com>
Added a new resource for Docker learning focused on React.js
development, including a discount code.
<!--Delete sections as needed -->
## Description
Added a new resource for Docker learning focused on React.js
development, including a discount code. My book Docker for React.js
developers.
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
---------
Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
## Description
Clarifies the wording in the "Persist the DB" workshop tutorial.
The volume is already created and named (`todo-db`) in step 1 using
`docker volume create`. The previous wording in step 3 suggested that
the volume was being named there, while the command actually uses the
existing volume as the mount source.
This change updates the wording to make the workflow clearer and more
technically accurate.
## Related issues or tickets
Fixes#25404
## Reviews
* [x] Technical review
* [ ] Editorial review
* [ ] Product review
- Python/Ruby GitHub Actions CI guides: 'is runs' -> 'runs', 'of you' ->
'of your', and 'Login to Docker Hub' link text -> 'Log in to Docker Hub'
- configure-builder: 'of you workflow' -> 'of your workflow'
- bind-mount page: remove stray article ('the a container' -> 'the container')
- pre-seeding guide: 'let you access to' -> 'letting you access', 'define' -> 'defines'
<!--Delete sections as needed -->
## Description
As per Craigs number-crunching, this PR removes some vvvvv old and
unused redirects 🧹
## 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
Replaces the goat ASCII-art registry/repository/image diagram with a
mermaid flowchart that uses nested subgraphs to express the same
containment hierarchy. Also exercises the new mermaid codeblock hook
so the layouts ship with at least one consumer.
<!--Delete sections as needed -->
## Description
Removing `docker init` workflow from guides. See ticket for more info.
Instead, have copy-paste codeblocks of the existing output. Added tip to
use Gordon.
## Related issues or tickets
ENGDOCS-3299
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Editorial review
---------
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
Added a new book recommendation for Docker enthusiasts.
Operation AI with Docker
- Introduce Docker-based AI development workflow
- Cover Docker Model Runner for local LLM execution
- Explain Docker offload capabilities for AI workloads
- Add KAGENS containers overview and usage patterns
- Describe running AI models inside isolated containers
- Include examples for local AI model deployment using Docker
- Demonstrate GPU/CPU acceleration setup for model inference
- Cover containerized environment setup for AI development
- Show practical use cases for AI experimentation locally
- Add developer-friendly workflows for reproducible AI systems
Replaces @material-symbols/svg-400 (5.5 MB) with heroicons (488 KB) — an
11x reduction in icon asset size. Heroicons uses a single consistent
distribution format (24px solid SVGs, fill="currentColor") eliminating
the need for the separate utils/svg.html partial, the icon-svg-stroke CSS
utility, and the dual-path resolution logic in icon.html.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
## Description
Removed unnecessary 'to' in the explanation of container port exposure.
This reads much better.
## Related issues or tickets
None.
## Reviews
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
## Description
Fixes a typo in the What's next page description by changing "hep" to
"help".
## Related issues or tickets
N/A
## Reviews
Docs-only, single-file change aligned with CONTRIBUTING.md general
guidelines.
Validation/testing: not run locally; no behavior change.
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
Co-authored-by: rohan436 <rohan.santhoshkumar@googlemail.com>
## 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>
This pull request fixes a minor subject–verb agreement issue in the
Docker platform overview documentation to improve grammatical clarity
and readability.
- replace old Docker desktop screenshot with the new sidebar
- Remove all references to Yarn in the explanation for Part 1
- Show new project directory structure for getting-started-repo
- Remove PWD reference from Part 3
- Remove all occurances of Yarn in Part 7 and 8
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
This PR is heavily dependent upon
https://github.com/docker/getting-started-app/pull/98
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Co-authored-by: Craig Osterhout <craig.osterhout@docker.com>
This PR adds minor adjustments to sign up procedures in prerequisite
sections.
* Adding one word `verified` to instances of `Docker account` in
prerequisite sections is a subtle, unobtrusive change that returning,
verified users can gloss over, while still prompting new users to verify
their email if they haven't yet.
* Changes stick to specific instances in `## Prerequisite` sections and
does not add `verified` to every instance (which would be obtrusive).
* Edits to Create Account doc to remove redundant callouts, consolidate
steps for shorter procedures, and add context about verification.
* If an instance of `Docker account` links to /create-account and not
the sign up page, I did not add `verification`.
* **Note**: we may want to consider a direct link to a sign up page
rather than linking them to a create account page. This can be a
separate PR, however.
<!--Delete sections as needed -->
## Description
This PR:
- Updates the old Spring Initializr screenshot page with the latest one
- Updates Spring Boot to 4.0.1 version
<!-- 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
Updated the Docker image layer output with the correct and latest size.
<!-- 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
This PR replaces old screenshots with the latest Node version.
<!-- 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
This PR:
- Replaces old Docker Desktop sidebar screenshots
- Updates the Volume section with the latest menu
- Updates psql CLI with the right version
- Adds New UI for scheduling Exports and Containers in-use
<!-- 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
This PR:
- Replaces `exec-into-container` image with the latest screenshot
- Replaces `inspecting-container` image with the latest screenshot
- Add DHI specific information to multiple pages
- Updates welcome-to-docker image details
<!-- 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
---------
Co-authored-by: Craig Osterhout <craig.osterhout@docker.com>
Fixed grammar issue
OLD LINE
Since containers are run in isolation, they have minimal influence on
the host and other containers, increasing the security of your
applications.
NEW LINE
Since containers run in isolation, they have minimal influence on the
host and other containers, increasing the security of your applications.
<!--Delete sections as needed -->
## Description
Added alias for old path.
## Related issues or tickets
Closes#23919
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Editorial review
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
## Summary
Adds a note to the Docker Compose tutorial clarifying that the
application may take 10-15 seconds to fully start after running `docker
compose up -d --build`.
## Changes
Updated step 5 in the "Start the application" section to inform users
that the application may not be immediately accessible at
`localhost:3000` and that they should wait a moment and refresh if the
page doesn't load right away.
## Why this change is needed
When users run `docker compose up`, Docker reports containers as
"Started" once they're running, but the applications inside (Node.js app
and MySQL database) still need time to initialize and connect. This
causes confusion for beginners who expect immediate accessibility after
seeing "Container started" in the CLI output or within the GUI.
## Related Issue
Fixes#23500
Co-authored-by: Andrew Hopp <ahopp@Andrews-Laptop.local>
