docker
Registry Mirror config and RAM conflict
Tell us about your request
registry-mirrors and RAM setting don't seem to work well together. Configuring a mirror for docker.io if you try and pull hello-world and docker.io restricted than the pull will fail. If a mirror is configured than try that first and use those registry endpoints, validate RAM on those still, and then docker.io.
Which service(s) is this request for? Docker Desktop Business
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? We have to nudge folks to use a mirror either by fully qualifying the path or using registry-mirrors.
Are you currently working around the issue? We just have to tell folks to fully qualify to avoid the RAM error
Additional context Using the install arg for admin-settings is brutal to make sure the JSON is properly formatted, quoted and embedded quotes are properly escaped. And if you get it wrong (cough forgot my brackets for a couple iterations) the errors it creates in DD are completely opaque.
--admin-settings="{\"configurationFileVersion\": 2,\"linuxVM\":{\"dockerDaemonOptions\":{\"value\":\"{\\\"registry-mirrors\\\":[\\\"https://docker.example.com\\\"]}\"}}}"
Fingers crossed use of Windows Registry policy key and Config prefs on macOS will come around as an alternative sometime soon.
Did trade some emails with Docker Support and currently the engine will check to see if the source docker.io version matches what is in the specified registry-mirror. And since RAM has a block on docker.io even if the mirror is appropriate the run will fail. So it would still be nice to have RAM work with mirrors so if the one in the mirror is fine it will source them. Given if we fully qualify the image it works fine even if the actual image is from docker.io it seems like it should be fine.