ts_image_restore_digest.md

copyright	lastupdated	keywords	subcollection	content-type
years 2017, 2024	2024-04-26	restore, image, digest, trash, tag, repository	Registry	troubleshoot

{{site.data.keyword.attribute-definition-list}}

Why aren't all the tags restored when I restore by digest in {{site.data.keyword.registryshort}}?

{: #troubleshoot-image-restore-digest} {: troubleshoot} {: support}

You want to restore an image by digest from the {{site.data.keyword.registrylong}} trash, but some tags weren't restored. {: shortdesc}

You run the ibmcloud cr image-restore command, but the tags were not restored. If all the tags were unsuccessful, the digest shows in the live repository, but it is not tagged. You can see the digest if you run ibmcloud cr image-digests, but not if you run ibmcloud cr image-list. {: tsSymptoms}

The tags that were not restored are already in your live repository. You can't overwrite a tag with a tag that is in the trash. {: tsCauses}

Remove the tag from the existing image in your live repository by running the ibmcloud cr image-untag command. You can then restore the required image from the trash by running the ibmcloud cr image-restore command with the option <repo>@<digest>, which restores the digest and its tags to the live repository. For more information, see Restoring images by digest. Alternatively, you can run the ibmcloud cr image-tag command and use the restored digest as the source image. {: tsResolve}

In your live repository, you can pull the image by digest. If you run the ibmcloud cr image-digests command, the image shows in the output. {: tip}