Skip to content

Conversation

@chaomonica
Copy link
Contributor

@chaomonica chaomonica commented Apr 22, 2025

Description

If a user has configured a mirror registry but has restricted Docker Hub in their RAM settings, they will get an error Access to docker.io has been restricted by your administrators. even if that image has already been cached in their registry mirror.

Related issues or tickets

SEG-1124 (Slack thread linked in ticket for context)

Reviews

Please do not merge until after technical review!

@karman-docker I have tested the commands in the following section. Could you please review "This happens because RAM restrictions are enforced at the API proxy layer, meaning that the request is blocked before Docker Desktop even attempts to pull from a registry mirror or fall back to Docker Hub."?

  • Technical review
  • Editorial review
  • Product review

@github-actions github-actions bot added the area/hub Issue affects Docker Hub label Apr 22, 2025
@netlify
Copy link

netlify bot commented Apr 22, 2025

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit dcaac70
🔍 Latest deploy log https://app.netlify.com/sites/docsdocker/deploys/6808f7fb5908600008a06548
😎 Deploy Preview https://deploy-preview-22474--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 site configuration.

@chaomonica chaomonica marked this pull request as ready for review April 22, 2025 22:36
Error response from daemon: Access to docker.io has been restricted by your administrators.
```

This happens because RAM restrictions are enforced at the API proxy layer, meaning that the request is blocked before Docker Desktop even attempts to pull from a registry mirror or fall back to Docker Hub.
Copy link
Contributor

@karman-docker karman-docker Apr 23, 2025

Choose a reason for hiding this comment

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

@chaomonica we can remove this part (line 57), as it is an implementation detail, end user need not know about it.

Copy link
Contributor

Choose a reason for hiding this comment

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

Also under Caveats in https://docs.docker.com/security/for-admins/hardened-desktop/registry-access-management/ we can add a link that points to the description here.

Copy link
Contributor

@aevesdocker aevesdocker left a comment

Choose a reason for hiding this comment

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

Thank you @chaomonica

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

Labels

area/hub Issue affects Docker Hub area/security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants