Questions and answers about Container Registry
Why is the "latest" tag missing or why is it assigned to a Docker image that wasn't the last one pushed?
The reason is that you specified a different tag when pushing the Docker image.
The Docker client assigns the latest tag automatically if the Docker image is created and pushed without a tag. You can also specify the latest tag explicitly.
Warning
The tag latest doesn't mean that the Docker image was the latest one pushed.
We don't recommend overwriting tags. Use a unique tag for each Docker image version. This way you can use the same Docker image version on all your VMs with identical specifications and more easily identify causes of problems.
How do I make a registry public?
You can issue the container-registry.images.puller role for your registry to the allUsers system group.
Alert
This makes all images in the registry available without authentication.
Don't assign the container-registry.images.pusher, editor or admin roles to the system group for the registry. This would allow anyone who learns your registry ID to use it at your expense.
I encountered an error. What should I do?
See Troubleshooting. It lists common errors and ways to solve them.
Can I get logs of my operations with services?
Yes, you can request log records about your resources from Yandex.Cloud services. For more information, see Data requests.