[Docs]: registry_auth for higher rate limits

mkdocs/docs/concepts/dev-environments.md

@@ -298,6 +298,9 @@ ide: vscode
 
 </div>
 
+??? info "Registry rate limits"
+    The `dstack` server queries the Docker registry for details about your custom image, such as its default user and entrypoint. If you are submitting many jobs and hitting the registry’s rate limit, try setting [`registry_auth`](../reference/dstack.yml/dev-environment.md#registry_auth), as many registries offer higher rate limits for authenticated users.
+
 ### Environment variables
 
 <div editor-title=".dstack.yml"> 

mkdocs/docs/concepts/services.md

@@ -993,6 +993,9 @@ resources:
   gpu: H100:1
 ```
 
+??? info "Registry rate limits"
+    The `dstack` server queries the Docker registry for details about your custom image, such as its default user and entrypoint. If you are submitting many jobs and hitting the registry’s rate limit, try setting [`registry_auth`](../reference/dstack.yml/service.md#registry_auth), as many registries offer higher rate limits for authenticated users.
+
 ### Working directory
 
 If `working_dir` is not specified, it defaults to the working directory set in the Docker image. For example, the [default image](#default-image) uses `/dstack/run` as its working directory.

mkdocs/docs/concepts/tasks.md

@@ -510,6 +510,9 @@ resources:
 !!! info "No commands"
     If `commands` are not specified, `dstack` runs `image`’s entrypoint (or fails if none is set).
 
+??? info "Registry rate limits"
+    The `dstack` server queries the Docker registry for details about your custom image, such as its default user and entrypoint. If you are submitting many jobs and hitting the registry’s rate limit, try setting [`registry_auth`](../reference/dstack.yml/task.md#registry_auth), as many registries offer higher rate limits for authenticated users.
+
 #### Docker in Docker
 
 Set `docker` to `true` to enable the `docker` CLI in your task, e.g., to run or build Docker images, or use Docker Compose.