Troubleshooting in Container Registry
See below for a list of common issues and their fixes:
-
docker login is not supported with yc credential helperWhy you got this error: If you are using a Docker credential helper, you cannot get authenticated in Container Registry with
docker login. You may also see the same error in Container Optimized Image where a credential helper is used for authentication as a service account linked to a VM.How to fix it: Get authenticated in the registry using a Docker credential helper or disable the Docker credential helper.
-
Got permission denied while trying to connect to the Docker daemon socketWhy you got this error: By default, the Docker daemon requires
rootpermissions to run commands.How to fix it: Run commands using
sudoor configure permissions for other OS users. -
name unknown: Registry <...> not foundWhy you got this error: 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: View the registry list to check your unique registry ID is valid.
-
Error response from daemon: pull access denied for <cr.yandex/registry_ID/Docker_image_name>, repository does not exist or may require 'docker login': denied: Permission denied ; requestId = <request_ID>Why you got this error: IP address sending the pull Docker image request has no PULL permissions.
How to fix it: Add rules that allow pulling images from this IP address in the registry settings or delete all rules and try again.
-
Error response from daemon: unauthorized: Authentication problem ; requestId = <request_ID>unauthorized: Authentication problem ; requestId = <request_ID>Why you got this error: You are trying to pull or push a Docker image to Container Registry, but you are not authenticated. To perform operations with images in Container Registry, you need to get authenticated first.
How to fix it: Get authenticated in Container Registry.