Troubleshooting in Container Registry

The most common errors and how to resolve them are listed below:

• docker login is not supported with yc credential helper

  Why the error occurred: If you use Docker credential helpers, you cannot get authenticated in Container Registry using your docker login. You can also see the same error in Container Optimized Image where a credential helper is used to authenticate on behalf of a service account linked to a VM.

  How to fix it: Get authenticated in the registry using Docker credential helper or disable Docker credential helper.

• Got permission denied while trying to connect to the Docker daemon socket

  Why the error occurred: The Docker daemon requires root permission to execute commands by default.

  Fix: Run commands using sudo or configure access for other operating system users.

• name unknown: Registry <...> not found

  Why the error occurred: The registry ID is missing or invalid. When using Docker CLI commands, you must specify the full name of a Docker image, including the registry ID. For more information, see Repository in Container Registry.

  How to fix it: Check the validity of your unique registry ID in the registry list.

• Error response from daemon: pull access denied for <cr.il.nebius.cloud/registry_ID/Docker_image_name>, repository does not exist or may require 'docker login': denied: Permission denied ; requestId = <request_ID>

  Why the error occurred: The IP address from which the pull Docker image request comes has no PULL permission.

  How to fix it: Add rules that allow pulling image for this IP in the registry settings or delete all rules and try again.