---
name: Registry-ts_docker_latest
title: Why can't I pull the newest image by using the `latest` tag in Container Registry?
description: You're unable to pull the most recent image by using the `latest` tag in IBM Cloud® Container Registry.
last-updated: 2025-10-17
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/Registry?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why can't I pull the newest image by using the `latest` tag in Container Registry?
{: #troubleshoot-docker-latest}
{: troubleshoot}
{: support}

You're unable to pull the most recent image by using the `latest` [tag](#x2040924){: term} in IBM Cloud® Container Registry.
{: shortdesc}

You're trying to run the `docker pull` command, but it returned a version of your image that isn't the most recent version built.
{: tsSymptoms}

The `latest` tag is applied by default to reference an image when you run Docker commands without specifying the tag value. The `latest` tag is applied to the most recent `docker build` or `docker tag` command that was run without a tag value explicitly set. Therefore, it's possible to run `docker` commands out of order or to explicitly set tags on some images. Both scenarios cause the `latest` tag to refer to a build that isn't the most recent.
{: tsCauses}

To make it easier to find the most recent image, define a different sequential tag for your images every time, and do not rely on the `latest` tag.
{: tsResolve}

To find the most recent image, you can run the `ibmcloud cr image-list` command rather than the `docker pull` command.

For more information about Docker tags, see [docker image tag](https://docs.docker.com/reference/cli/docker/image/tag/){: externa}.