Skip to content

Commit 63ade45

Browse files
refresh: admin guides (#23606)
## Description - Gave the admin guides a refresh and polish ## Related issues or tickets https://docker.atlassian.net/browse/ENGDOCS-3079 --------- Co-authored-by: David Karlsson <[email protected]>
1 parent 75fcd57 commit 63ade45

File tree

10 files changed

+279
-128
lines changed

10 files changed

+279
-128
lines changed
Lines changed: 64 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
title: Set up your company for success with Docker
3-
linkTitle: Admin set up
3+
linkTitle: Admin set up
44
summary: Get the most out of Docker by streamlining workflows, standardizing development environments, and ensuring smooth deployments across your company.
55
description: Learn how to onboard your company and take advantage of all of the Docker products and features.
66
tags: [admin]
77
params:
88
featured: true
99
time: 20 minutes
10-
image:
10+
image:
1111
resource_links:
1212
- title: Overview of Administration in Docker
1313
url: /admin/
@@ -27,42 +27,82 @@ params:
2727
url: /subscription/details/
2828
---
2929

30-
Docker's tools provide a scalable, secure platform that empowers your developers to create, ship, and run applications faster. As an administrator, you have the ability to streamline workflows, standardize development environments, and ensure smooth deployments across your organization.
30+
Docker's tools provide a scalable, secure platform that empowers your
31+
developers to create, ship, and run applications faster. As an administrator,
32+
you can streamline workflows, standardize development environments, and ensure
33+
smooth deployments across your organization.
3134

32-
By configuring Docker products to suit your company’s needs, you can optimize performance, simplify user management, and maintain control over resources. This guide will help you set up and configure Docker products to maximize productivity and success for your team whilst meeting compliance and security policies
35+
By configuring Docker products to suit your company's needs, you can optimize
36+
performance, simplify user management, and maintain control over resources.
37+
This guide helps you set up and configure Docker products to maximize
38+
productivity and success for your team while meeting compliance and security
39+
policies.
3340

3441
## Who’s this for?
3542

36-
- Administrators responsible for managing Docker environments within their organization
43+
- Administrators responsible for managing Docker environments within their
44+
organization
3745
- IT leaders looking to streamline development and deployment workflows
3846
- Teams aiming to standardize application environments across multiple users
39-
- Organizations seeking to optimize their use of Docker products for greater scalability and efficiency
40-
- Organizations with [Docker Business subscriptions](https://www.docker.com/pricing/).
47+
- Organizations seeking to optimize their use of Docker products for greater
48+
scalability and efficiency
49+
- Organizations with a
50+
[Docker Business subscription](https://www.docker.com/pricing/)
4151

4252
## What you’ll learn
4353

44-
- The importance of signing in to the company's Docker organization for access to usage data and enhanced functionality.
45-
- How to standardize Docker Desktop versions and settings to create a consistent baseline for all users, while allowing flexibility for advanced developers.
46-
- Strategies for implementing Docker’s security configurations to meet company IT and software development security requirements without hindering developer productivity.
54+
- Why signing into your company's Docker organization provides access to usage
55+
data and enhanced functionality
56+
- How to standardize Docker Desktop versions and settings to create a consistent
57+
baseline for all users, while allowing flexibility for advanced developers
58+
- Strategies for implementing Docker's security configurations to meet company
59+
IT and software development security requirements without hindering developer productivity
4760

4861
## Features covered
4962

50-
- Organizations. These are the core structure for managing your Docker environment, grouping users, teams, and image repositories. Your organization was created with your subscription and is managed by one or more Owners. Users signed into the organization are assigned seats based on the purchased subscription.
51-
- Enforce sign-in. By default, Docker Desktop does not require sign-in. However, you can configure settings to enforce this and ensure your developers sign in to your Docker organization.
52-
- SSO. Without SSO, user management in a Docker organization is manual. Setting up an SSO connection between your identity provider and Docker ensures compliance with your security policy and automates user provisioning. Adding SCIM further automates user provisioning and de-provisioning.
53-
- General and security settings. Configuring key settings will ensure smooth onboarding and usage of Docker products within your environment. Additionally, you can enable security features based on your company's specific security needs.
63+
This guide covers the following Docker features:
5464

55-
## Who needs to be involved?
65+
- [Organizations](/manuals/admin/organization/_index.md): The core structure
66+
for managing your Docker environment, grouping users, teams, and image
67+
repositories. Your organization was created with your subscription and is
68+
managed by one or more owners. Users signed into the organization are
69+
assigned seats based on the purchased subscription.
70+
- [Enforce sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md):
71+
By default, Docker Desktop doesn't require sign-in. You can configure
72+
settings to enforce this and ensure your developers sign in to your
73+
Docker organization.
74+
- [SSO](/manuals/enterprise/security/single-sign-on/_index.md): Without SSO,
75+
user management in a Docker organization is manual. Setting
76+
up an SSO connection between your identity provider and Docker ensures
77+
compliance with your security policy and automates user provisioning. Adding
78+
SCIM further automates user provisioning and de-provisioning.
79+
- General and security settings: Configuring key settings ensures smooth
80+
onboarding and usage of Docker products within your environment. You can also
81+
enable security features based on your company's specific security needs.
5682

57-
- Docker organization owner: A Docker organization owner must be involved in the process and will be required for several key steps.
58-
- DNS team: The DNS team is needed during the SSO setup to verify the company domain.
59-
- MDM team: Responsible for distributing Docker-specific configuration files to developer machines.
60-
- Identity Provider team: Required for configuring the identity provider and establishing the SSO connection during setup.
61-
- Development lead: A development lead with knowledge of Docker configurations to help establish a baseline for developer settings.
62-
- IT team: An IT representative familiar with company desktop policies to assist with aligning Docker configuration to those policies.
63-
- Infosec: A security team member with knowledge of company development security policies to help configure security features.
64-
- Docker testers: A small group of developers to test the new settings and configurations before full deployment.
83+
## Who needs to be involved
84+
85+
- Docker organization owner: Must be involved in the process and is required
86+
for several key steps
87+
- DNS team: Needed during the SSO setup to verify the company domain
88+
- MDM team: Responsible for distributing Docker-specific configuration files to
89+
developer machines
90+
- Identity Provider team: Required for configuring the identity provider and
91+
establishing the SSO connection during setup
92+
- Development lead: A development lead with knowledge of Docker configurations
93+
to help establish a baseline for developer settings
94+
- IT team: An IT representative familiar with company desktop policies to
95+
assist with aligning Docker configuration to those policies
96+
- Infosec: A security team member with knowledge of company development
97+
security policies to help configure security features
98+
- Docker testers: A small group of developers to test the new settings and
99+
configurations before full deployment
65100

66101
## Tools integration
67102

68-
Okta, Entra ID SAML 2.0, Azure Connect (OIDC), MDM solutions like Intune
103+
This guide covers integration with:
104+
105+
- Okta
106+
- Entra ID SAML 2.0
107+
- Azure Connect (OIDC)
108+
- MDM solutions like Intune

content/guides/admin-set-up/comms-and-info-gathering.md

Lines changed: 54 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -4,30 +4,71 @@ description: Gather your company's requirements from key stakeholders and commun
44
weight: 10
55
---
66

7-
## Step one: Communicate with your developers and IT teams
7+
## Communicate with your developers and IT teams
88

9-
### Docker user communication
9+
Before rolling out Docker Desktop across your organization, coordinate with key stakeholders to ensure a smooth transition.
1010

11-
You may already have Docker Desktop users within your company, and some steps in this process may affect how they interact with the platform. It's highly recommended to communicate early with users, informing them that as part of the subscription onboarding, they will be upgraded to a supported version of Docker Desktop.
11+
### Notify Docker Desktop users
1212

13-
Additionally, communicate that settings will be reviewed to optimize productivity, and users will be required to sign in to the company’s Docker organization using their business email to fully utilize the subscription benefits.
13+
You may already have Docker Desktop users within your company. Some steps in
14+
this onboarding process may affect how they interact with the platform.
1415

15-
### MDM team communication
16+
Communicate early with users to inform them that:
1617

17-
Device management solutions, such as Intune and Jamf, are commonly used for software distribution across enterprises, typically managed by a dedicated MDM team. It is recommended that you engage with this team early in the process to understand their requirements and the lead time for deploying changes.
18+
- They'll be upgraded to a supported version of Docker Desktop as part of the subscription onboarding
19+
- Settings will be reviewed and optimized for productivity
20+
- They'll need to sign in to the company's Docker organization using their
21+
business email to access subscription benefits
1822

19-
Several key setup steps in this guide require the use of JSON files, registry keys, or .plist files that need to be distributed to developer machines. It’s a best practice to use MDM tools for deploying these configuration files and ensuring their integrity is preserved.
23+
### Engage with your MDM team
2024

21-
## Step two: Identify Docker organizations
25+
Device management solutions, such as Intune and Jamf, are commonly used for
26+
software distribution across enterprises. These tools are typically managed by a dedicated MDM team.
2227

23-
Some companies may have more than one [Docker organization](/manuals/admin/organization/_index.md) created. These organizations may have been created for specific purposes, or may not be needed anymore. If you suspect your company has more than one Docker organization, it's recommended you survey your teams to see if they have their own organizations. You can also contact your Docker Customer Success representative to get a list of organizations with users whose emails match your domain name.
28+
Engage with this team early in the process to:
2429

25-
## Step three: Gather requirements
30+
- Understand their requirements and lead time for deploying changes
31+
- Coordinate the distribution of configuration files
2632

27-
Through [Settings Management](/manuals/enterprise/security/hardened-desktop/settings-management/_index.md), Docker provides numerous configuration parameters that can be preset. The Docker organization owner, development lead, and infosec representative should review these settings to establish the company’s baseline configuration, including security features and [enforcing sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md) for Docker Desktop users. Additionally, they should decide whether to take advantage of other Docker products, such as [Docker Scout](/manuals/scout/_index.md), which is included in the subscription.
33+
Several setup steps in this guide require JSON files, registry keys, or .plist
34+
files to be distributed to developer machines. Use MDM tools to deploy these configuration files and ensure their integrity.
35+
36+
## Identify Docker organizations
37+
38+
Some companies may have more than one
39+
[Docker organization](/manuals/admin/organization/_index.md) created. These
40+
organizations may have been created for specific purposes, or may not be
41+
needed anymore.
42+
43+
If you suspect your company has multiple Docker organizations:
44+
45+
- Survey your teams to see if they have their own organizations
46+
- Contact your Docker Support to get a list of organizations with users whose
47+
emails match your domain name
48+
49+
## Gather requirements
50+
51+
[Settings Management](/manuals/enterprise/security/hardened-desktop/settings-management/_index.md) lets you preset numerous configuration parameters for Docker Desktop.
52+
53+
Work with the following stakeholders to establish your company's baseline
54+
configuration:
55+
56+
- Docker organization owner
57+
- Development lead
58+
- Information security representative
59+
60+
Review these areas together:
61+
62+
- Security features and
63+
[enforcing sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md)
64+
for Docker Desktop users
65+
- Additional Docker products included in your subscriptions
2866

2967
To view the parameters that can be preset, see [Configure Settings Management](/manuals/enterprise/security/hardened-desktop/settings-management/configure-json-file.md#step-two-configure-the-settings-you-want-to-lock-in).
3068

31-
## Optional step four: Meet with the Docker Implementation team
69+
## Optional: Meet with the Docker Implementation team
70+
71+
The Docker Implementation team can help you set up your organization,
72+
configure SSO, enforce sign-in, and configure Docker Desktop.
3273

33-
The Docker Implementation team can help you step through setting up your organization, configuring SSO, enforcing sign-in, and configuring Docker. You can reach out to set up a meeting by emailing [email protected].
74+
To schedule a meeting, email [email protected].
Lines changed: 24 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,35 @@
11
---
2-
title: Deploy
2+
title: Deploy your Docker setup
33
description: Deploy your Docker setup across your company.
44
weight: 40
55
---
66

77
> [!WARNING]
8-
> Ensure you communicate with your users before proceeding, and confirm that your IT and MDM teams are prepared to handle any unexpected issues, as these steps will affect all existing users signing into your Docker organization.
8+
>
9+
> Communicate with your users before proceeding, and confirm that your IT and
10+
MDM teams are prepared to handle any unexpected issues, as these steps will
11+
affect all existing users signing into your Docker organization.
912

10-
## Step one: Enforce SSO
13+
## Enforce SSO
1114

12-
Enforcing SSO means that anyone who has a Docker profile with an email address that matches your verified domain must sign in using your SSO connection. Make sure the Identity provider groups associated with your SSO connection cover all the developer groups that you want to have access to the Docker subscription.
15+
Enforcing SSO means that anyone who has a Docker profile with an email address
16+
that matches your verified domain must sign in using your SSO connection. Make
17+
sure the Identity provider groups associated with your SSO connection cover all
18+
the developer groups that you want to have access to the Docker subscription.
1319

14-
## Step two: Deploy configuration settings and enforce sign-in to users
20+
For instructions on how to enforce SSO, see [Enforce SSO](/manuals/enterprise/security/single-sign-on/connect.md).
1521

16-
Have the MDM team deploy the configuration files for Docker to all users.
22+
## Deploy configuration settings and enforce sign-in to users
1723

18-
Congratulations, you have successfully completed the admin implementation process for Docker.
24+
Have the MDM team deploy the configuration files for Docker to all users.
25+
26+
## Next steps
27+
28+
Congratulations, you've successfully completed the admin implementation process
29+
for Docker.
30+
31+
To continue optimizing your Docker environment:
32+
33+
- Review your [organization's usage data](/manuals/admin/organization/insights.md) to track adoption
34+
- Monitor [Docker Scout findings](/manuals/scout/explore/analysis.md) for security insights
35+
- Explore [additional security features](/manuals/enterprise/security/_index.md) to enhance your configuration

0 commit comments

Comments
 (0)