Enforce sign-in for Docker Sandboxes
Organization policies apply only when a developer signs in to Docker Sandboxes as a member of your organization. Without sign-in enforcement, a developer can sign in with a personal account and bypass those policies. Sign-in enforcement closes that gap on the machine itself, where users can't override it.
To set it up, you write an enforcement configuration that lists your organizations, test it on one machine, then deploy it to your developers' machines with your endpoint management tooling.
How sign-in enforcement works
- An administrator deploys an enforcement configuration to managed endpoints through MDM, Group Policy, or configuration management, specifying one or more allowed Docker organization slugs.
- When a user runs
sbx login, they authenticate with Docker. Credentials are saved temporarily, then Docker Sandboxes calls the Docker API to verify organization membership. - If the user belongs to at least one allowed organization, sign-in succeeds and the credentials are kept.
- If not, Docker Sandboxes immediately revokes the saved credentials and the user receives a denial message listing the required organizations.
sbx login and sbx logout always run regardless of organization membership.
Other commands require a valid signed-in session, so they fail after a denied
sign-in until the user signs in with an allowed account.
Write the enforcement configuration
The configuration lists the organizations developers must belong to, and optionally who to contact for access. Every platform uses the same fields. The canonical JSON representation:
{
"allowedOrgs": ["docker", "acme-corp"],
"adminEmail": "it-security@acme-corp.com",
"adminURL": "https://acme-corp.atlassian.net/servicedesk/it",
"adminName": "ACME IT Security Team"
}| Field | Type | Required | Description |
|---|---|---|---|
allowedOrgs | list of strings | Yes | Docker organization slugs. The user must be a member of at least one. Matching is case-insensitive. |
adminName | string | No | Administrator or team display name shown in the denial message. |
adminEmail | string | No | Contact email shown in the denial message. |
adminURL | string | No | Help desk or access-request URL shown in the denial message. |
If allowedOrgs is empty or missing, enforcement is inactive and any
authenticated user can use Docker Sandboxes.
The optional adminName, adminEmail, and adminURL fields give denied users
a path to resolution. Include the contact details your organization uses for
access requests.
Test the configuration on one machine
Before you deploy to every machine, write the configuration on one machine and
confirm that sbx login behaves as you expect.
Write the configuration to the user preferences domain:
$ defaults write com.docker.sbx allowedOrgs -array "acme-corp"
$ defaults write com.docker.sbx adminEmail "it@acme.com"
To remove the test configuration:
$ defaults delete com.docker.sbx
defaults write uses the user preferences domain, not the managed-preferences
domain. On a managed device, the MDM profile is authoritative and user-level
settings in the same domain are ignored.
Run the following in an elevated PowerShell session. Use New-ItemProperty to
create values with an explicit type. Set-ItemProperty doesn't create new
values.
New-Item -Path "HKLM:\SOFTWARE\Policies\Docker\SBX" -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Docker\SBX" `
-Name "allowedOrgs" -Value @("acme-corp") -PropertyType MultiString -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Docker\SBX" `
-Name "adminEmail" -Value "it@acme.com" -PropertyType String -ForceTo remove the test configuration:
Remove-Item -Path "HKLM:\SOFTWARE\Policies\Docker\SBX" -Recurse -ForceWrite the configuration file and set its ownership:
$ sudo mkdir -p /etc/docker-sbx
$ sudo tee /etc/docker-sbx/config.json <<'EOF'
{"allowedOrgs": ["acme-corp"], "adminEmail": "it@acme.com"}
EOF
$ sudo chown root:root /etc/docker-sbx/config.json
$ sudo chmod 644 /etc/docker-sbx/config.json
To remove the test configuration:
$ sudo rm -f /etc/docker-sbx/config.json
Then run sbx login with an account that belongs to an allowed organization,
and again with one that doesn't. The second sign-in is denied with the message
described in
Check what denied developers see.
Deploy the configuration to your managed machines
Use your existing endpoint management tooling to deploy the configuration. Each platform reads it from a native location that ordinary users can't modify.
On macOS, the configuration is a managed preferences domain, com.docker.sbx.
Deploy it through any MDM solution, such as Jamf or Intune, as a custom configuration profile. MDM-deployed profiles take precedence over user-level preferences and can only be removed by removing the device from MDM management, so users can't override them.
The following .mobileconfig payload sets the allowed organization and admin
contact details:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>PayloadContent</key>
<array>
<dict>
<key>PayloadType</key>
<string>com.apple.ManagedClient.preferences</string>
<key>PayloadVersion</key>
<integer>1</integer>
<key>PayloadIdentifier</key>
<string>com.docker.sbx.policy</string>
<key>PayloadUUID</key>
<string><!-- generate a UUID --></string>
<key>PayloadEnabled</key>
<true/>
<key>PayloadDisplayName</key>
<string>Docker Sandboxes Policy</string>
<key>PayloadContent</key>
<dict>
<key>com.docker.sbx</key>
<dict>
<key>Forced</key>
<array>
<dict>
<key>mcx_preference_settings</key>
<dict>
<key>allowedOrgs</key>
<array>
<string>acme-corp</string>
</array>
<key>adminEmail</key>
<string>it-security@acme-corp.com</string>
<key>adminURL</key>
<string>https://acme-corp.atlassian.net/servicedesk/it</string>
<key>adminName</key>
<string>ACME IT Security</string>
</dict>
</dict>
</array>
</dict>
</dict>
</dict>
</array>
</dict>
</plist>On Windows, the configuration is a set of registry values under
HKLM\SOFTWARE\Policies\Docker\SBX. Deploy them through Group Policy, Intune,
or any endpoint management tool that can write registry values.
| Value name | Type | Description |
|---|---|---|
allowedOrgs | REG_MULTI_SZ | Multi-string list, one organization slug per string |
adminName | REG_SZ | Administrator or team name (optional) |
adminEmail | REG_SZ | Contact email (optional) |
adminURL | REG_SZ | Help desk URL (optional) |
On Linux, the configuration is a root-owned JSON file at
/etc/docker-sbx/config.json.
Deploy it through configuration management such as Ansible, Puppet, Chef, or
Salt. The file must be owned by root with 644 permissions.
{
"allowedOrgs": ["acme-corp"],
"adminEmail": "it-security@acme-corp.com",
"adminURL": "https://acme-corp.atlassian.net/servicedesk/it",
"adminName": "ACME IT Security"
}The Linux loader fails closed if the file is a symlink, isn't a regular file,
isn't owned by root, or is writable by group or other. Any deviation is treated
as a configuration error and sbx login is denied with a descriptive message.
Deploying with the commands in
Test the configuration on one machine
passes these checks.
Check what denied developers see
When a user signs in with an account that isn't a member of an allowed
organization, they're signed out and shown a denial message. Only the contact
fields you configure appear. For example, if only adminEmail is set, the URL
line is omitted.
When no admin contact details are configured:
Access denied: Your administrator requires you to be logged into an account
that is a member of one of the following Docker organizations:
- acme-corp
Sign in with an account that belongs to one of these organizations, or
contact your administrator for access.When admin contact details are configured:
Access denied: Your administrator requires you to be logged into an account
that is a member of one of the following Docker organizations:
- acme-corp
For access, contact ACME IT Security:
Email: it-security@acme-corp.com
URL: https://acme-corp.atlassian.net/servicedesk/itTurn off enforcement
To turn off sign-in enforcement on a machine, remove the configuration with
the same tooling you used to deploy it. You can also leave allowedOrgs empty,
which makes enforcement inactive so any authenticated user can use Docker
Sandboxes.