Add clarifications about docker.io as a registry source or destination (

#362) add clarifications about docker.io as a registry source or destination
dotnet · Feb 28, 2023 · d838d43 · d838d43
1 parent 827fbf6
commit d838d43
Showing 1 changed file with 8 additions and 1 deletion.
diff --git a/docs/RegistryAuthentication.md b/docs/RegistryAuthentication.md
@@ -46,4 +46,11 @@ None! We're compatible with most registries.
 
 ### Docker Hub
 
-When using Docker Hub as a base image registry (via ContainerBaseImage) or as the destination registry for pushing your images, you must use the `registry-1.docker.io` domain name instead of `docker.io`. The `docker.io` domain does not respond to the Registry API in the expected way.
+When using Docker Hub as a base image registry (via ContainerBaseImage) or as the destination registry for pushing your images (via ContainerRegistry), you must use the one of the URLs that point to the _registry_ portion of Docker Hub. This means one of the following domains must be used:
+
+* `registry.hub.docker.com`
+* `registry-1.docker.io`
+
+The `docker.io` domain doesn't support the Registry API, so attempting to use it will result in errors.
+
+In addition, you should be sure to login via `docker login registry.hub.docker.com` or `docker login registry-1.docker.io` and not `docker login docker.io`, to ensure that the correct credentials are used by the tooling.