Skip to content

HD freshness#24666

Merged
aevesdocker merged 3 commits intodocker:mainfrom
aevesdocker:HD-freshness-2026
Apr 8, 2026
Merged

HD freshness#24666
aevesdocker merged 3 commits intodocker:mainfrom
aevesdocker:HD-freshness-2026

Conversation

@aevesdocker
Copy link
Copy Markdown
Contributor

Description

Related issues or tickets

Reviews

  • Technical review
  • Editorial review
  • Product review

@netlify
Copy link
Copy Markdown

netlify bot commented Apr 8, 2026

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 861e3f4
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/69d6723aa8816000087a35d3
😎 Deploy Preview https://deploy-preview-24666--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@aevesdocker
Copy link
Copy Markdown
Contributor Author

/review

Copy link
Copy Markdown
Contributor

@docker-agent docker-agent bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assessment: 🟢 APPROVE

This PR updates Hardened Desktop documentation for freshness. All changes follow Docker's documentation style guidelines and maintain consistency with existing content.

Changes reviewed:

  • Updated descriptions and keywords for better SEO
  • Removed version-specific callouts for older Docker Desktop versions
  • Improved clarity in prerequisites and configuration steps
  • Standardized terminology (e.g., "allowlist" instead of "allow list")
  • Added navigation aids ("Next steps" sections)
  • Updated front matter weights for better organization

No issues found. The documentation is clear, accurate, and follows the style guide.

@aevesdocker aevesdocker marked this pull request as ready for review April 8, 2026 13:38
@aevesdocker aevesdocker requested a review from akristen April 8, 2026 13:38
- A Docker Business subscription

Docker Desktop only applies settings from the `admin-settings.json` file when both authentication and Docker Business license checks succeed.
The presence of the `admin-settings.json` file enforces sign-in on Docker Desktop. This is intended for business features that require authentication.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to link out to the enforce sign in doc? not sure if these are the same mechanisms, or different mechanisms for the same outcome (or entirely unrelated)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tis the same as the enforce sign-in bullet point linked above, so I think we're good here


- `FindProxyForURL` function URL parameter format is http://host_or_ip:port or https://host_or_ip:port
- If you have an internal container trying to access https://docs.docker.com/enterprise/security/hardened-desktop/air-gapped-containers the docker proxy service will submit docs.docker.com for the host value and https://docs.docker.com:443 for the url value to FindProxyForURL, if you are using `shExpMatch` function in your PAC file as follows:
- If you have an internal container trying to access https://docs.docker.com/enterprise/security/hardened-desktop/air-gapped-containers the Docker proxy service will submit docs.docker.com for the host value and https://docs.docker.com:443 for the url value to `FindProxyForURL`, if you are using `shExpMatch` function in your PAC file as follows:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this meant to be a value, or a link? Maybe put in `s or link...ify it?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good spot!


> [!NOTE]
>
> Image Access Management is turned off by default. Organization owners have access to all images regardless of policy settings.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it tuned off by default, but Org owners still have access regardless of policy settings? Does this mean it's only tuned off to org members?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oo have clarified!

## Best practices

- Start with the most restrictive policy and gradually expand based on legitimate business needs:
1. Start with Docker Official Images and Organization images
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be

?

(I see this pattern in the docs i edit and the fussy ai bot yells at me when i don't use it lol)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh this is a list of just 1s....anyway

When namespace access control is enabled, organization members can still view and pull images
from their personal namespaces and continue accessing all existing repositories
and content. However, they will no longer be able to create new repositories or
and content. However, they are no longer able to create new repositories or
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
and content. However, they are no longer able to create new repositories or
and content. However, they're unable to create new repositories or

Copy link
Copy Markdown
Contributor

@akristen akristen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a few fussy comments; otherwise lgtm

- Data loss prevention: Block containers from uploading sensitive data to external services
- Supply chain security: Control which external resources containers can access during builds
- Corporate network policies: Enforce existing network security policies for containerized applications
- Your organisation requires containers to communicate only with approved internal services
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Your organisation requires containers to communicate only with approved internal services
- Your organization requires containers to communicate only with approved internal services

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok im not trying to assert the US spelling i think we have it in our style guide but i could be mistaken...

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you're not wrong...weird how the ai bot didn't pick this up

@aevesdocker aevesdocker merged commit 75ad2e5 into docker:main Apr 8, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants