Skip to content

Latest commit

 

History

History
50 lines (33 loc) · 1.74 KB

ts_manifest_error_version.md

File metadata and controls

50 lines (33 loc) · 1.74 KB
copyright lastupdated keywords subcollection content-type
years
2017, 2024
2024-04-25
error, registry, manifest version, manifest version error, tag, image, the manifest version for this image is not supported for tagging, CRI0301E
Registry
troubleshoot

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

Why do I get a manifest version error in {{site.data.keyword.registryshort_notm}}?

{: #troubleshoot-manifest-error-version} {: troubleshoot} {: support}

When you try to tag your image in {{site.data.keyword.registrylong}}, you get a manifest version error: CRI0301E The manifest version for this image is not supported for tagging. {: shortdesc}

You tried to tag your image, but you receive the following error message: CRI0301E The manifest version for this image is not supported for tagging. To upgrade to a supported manifest version, pull and push this image by using Docker version 17.07 or later, then run the 'ibmcloud cr image-tag' command again. {: tsSymptoms}

The manifest version is not supported. {: tsCauses}

To resolve the problem, complete the following steps: {: tsResolve}

  1. Upgrade to a supported version of Docker, see Support for Docker.

  2. Pull the image that you tried to tag by running the following command, where <source_image> is your source image name:

    docker pull <source_image>

    {: pre}

  3. To upgrade the manifest version, push the image by running the following command:

    docker push <source_image>

    {: pre}

  4. Tag the image by running the ibmcloud cr image-tag command, see Creating new images that refer to a source image.