David KarlssonandCodex
b98c400647
## 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>
3.5 KiB
title, linkTitle, description, keywords, weight
| title | linkTitle | description | keywords | weight |
|---|---|---|---|---|
| Roll out Docker to a pilot group | Pilot an organization rollout | Invite a pilot user, apply a Docker Desktop settings policy, and verify the managed experience before a wider deployment. | Docker, get started, administration, organization setup, pilot deployment, Settings Management | 3 |
Rolling out Docker across an organization changes how developers sign in and how Docker Desktop behaves. Testing the managed experience with a small group helps uncover access or workflow problems before they affect everyone.
In this 15-minute tutorial, you'll invite one pilot user, apply one managed setting to that user, and confirm that Docker Desktop receives the policy.
Before you start
You need:
- A Docker Business subscription
- Owner access to a Docker organization
- A verified company domain
- Enforced Docker Desktop sign-in
- One pilot user with Docker Desktop installed
Invite the pilot user
- Sign in to Docker Home and select your organization.
- Select Members, then Invite.
- Select Emails or usernames and enter the pilot user's email address.
- Assign the Member role and a Docker Desktop license, then send the invitation.
- Have the pilot user accept the invitation from the email or the Notifications Center.
The pilot user is now part of the organization and can receive its Docker Desktop policies.
Create a pilot policy
- In Docker Home, select Docker Desktop, then Settings Management.
- Select Create a settings policy.
- Name the policy
Docker pilot. - Apply the policy to Specific users, then select the pilot user.
- Set Automatically update components to Always enabled. Leave the other settings as User-defined.
- Select Create.
This policy locks one low-impact setting, making the result visible without changing the pilot user's development workflow.
Apply and verify the policy
Ask the pilot user to:
- Quit Docker Desktop completely.
- Start Docker Desktop and sign in with the account that joined the organization.
- Open Docker Desktop settings and confirm that Automatically update components is enabled and can't be changed.
- Run a familiar development project to confirm their normal workflow still works.
Docker Desktop checks for policy updates when it starts and every 60 minutes while running. Fully quitting and reopening it applies the policy without waiting for the next check.
What you learned
You added a user, targeted a policy, and verified the managed Docker Desktop experience before applying controls across the organization. Use the pilot's feedback to refine the policy and its deployment communication.
What's next
Continue with these guides when you're ready to expand the deployment:
- Set up your company for success with Docker for the full deployment handbook
- Manage organization members for roles, teams, and bulk invitations
- Configure Settings Management for additional policies and deployment controls
- Set up SSO and provisioning for centralized identity management
- Govern Docker Sandboxes for organization-wide agent policies