How to know which version of docker image is behind latest tag?

Related searches

I am working with two docker images of tensorflow (latest and latest-gpu tags):

FROM tensorflow/tensorflow:latest-gpu

and:

FROM tensorflow/tensorflow:latest

In order to not have surprises in the future, I would like to set the version of these two images.

On docker hub, I can't find this information in the tags pages: for example, latest would correspond to the 1.8.0-gpu tag.

Do you know if and where I can find this information?

Thank you,

Alexandre

What's Wrong With The Docker :latest Tag? � vsupalov.com, Docker images tagged with :latest have caused many people a lot of trouble. that :latest always points to the most-recently-pushed version of an image. I'm weary of using latest on a team as I can see somebody forgetting to tag a build get an overview of Docker and understand the "why" behind container technology. If you’re looking for a way to tag your Docker images, a safe bet is to use the Git commit hash as the image tag. This way, you will be able to: Tell immediately what code version is running based on the image tag. Roll back and deploy new versions of your app. Avoid naming collisions among developers.

is kinda BULLPOOP actually that docker do NOT do what is minimum of good sense and report such thing, and unfortunately the only solution I seem to find is ... oh well, ACTUALLY FISHING:

go to image webpage (nigix in my case) https://hub.docker.com/_/nginx then press tags tab, go to any latest, and copy sha256 sum then sort by newest, then scroll down until first numbered version and check if the exact same sha256 is displayed

now ... STILL after that fishing, there library/nginxit comes a sure thing:

you can verify if you did it right, for example now I manage to find that nginx:latest is actually 1.17.8, so, I run:

docker pull nginx:1.17.8
1.17.8: Pulling from library/nginx
bc51dd8edc1b: Pull complete
66ba67045f57: Pull complete
bf317aa10aa5: Pull complete
Digest:sha256:ad5552c786f128e389a0263104ae39f3d3c7895579d45ae716f528185b36bc6f
Status: Downloaded newer image for nginx:1.17.8

and then I verify by atempt to pull latest:

docker pull nginx:latest
latest: Pulling from library/nginx
Digest: sha256:ad5552c786f128e389a0263104ae39f3d3c7895579d45ae716f528185b36bc6f
Status: Downloaded newer image for nginx:latest

how you can see it didn't actually pull anything, and sha256 is the exact same ;)

The misunderstood Docker tag: latest | by Marc Campbell, Docker images have a tag named latest which doesn't work as you expect. I've listened to numerous speakers and Docker 101 talks only to see this this image to Docker Hub, I'm going to build, tag and version my image. The trick is of course, if you leave the tag part out (e.g. _docker tag myrepo:1.0 myrepo), Docker will automatically give it the tag latest. You probably knew all this already, but it's important to realise that this is about as far as it goes -- the latest tag doesn't have any magical powers.

Devel docker images include all the necessary dependencies to build from source whereas the other binaries simply have TensorFlow installed.

docker image history, docker image save, Save one or more images to a tar archive (streamed to STDOUT by default). docker image tag, Create a tag TARGET_IMAGE that refers to� 'docker search ' command lists only the matching images in the registry, not the version (tags). I wanted to know the tag history of the given image. One way to know this detail is to go to Docker Hub or GitHub folders for the image and deduce previous versions from Dockerfile.

docker tag, If you are behind an HTTP proxy server, for example in corporate settings, docker pull debian Using default tag: latest latest: Pulling from library/debian To see which images are present locally, use the docker images command: When pulling an image by digest, you specify exactly which version of an image to pull. Docker images have a tag named latest which doesn’t work as you expect. I’ve listened to numerous speakers and Docker 101 talks only to see this misrepresented too often. Because tags and

docker pull, Supposed I have an image that I want to tag as 0.10.24 (in my case it's an image containing Node.js 0.10.24). I built that image using a Dockerfile and executing docker build and by providing a tag

If you don’t add a tag, the tag latest is implied. The latest tag does not necessarily mean it will download the most recent version of the image. When the latest tag is used, docker daemon will download the image tagged as latest. For example, ubuntu:latest tag points to the "latest LTS" release rather than the most recent release.

Comments
  • Take a look at this: The misunderstood Docker tag: latest. It concludes at "Don’t use it. Don’t be tempted by it. It’s easy to look at it and think that your deployment script should just pull "latest" and your build process will ensure that’s valid. It takes a lot of discipline to make that work. Just version your tags. Every time."
  • I read it already :) I totally agree with him. I now would like to use versioned tags but I can't find what the latest tag actually refers to.
  • this is a super hyper specific answer to this particular image, wouldn't be better to have shell or python script parse the above said tags HTML page from a CLI to try and determine which version the latest tag corresponds to?
  • The question was related to obtaining the info about exact version instead of using latest to set it to fixed value to avoid surprises. If you would extract latest info automatically, then you could use latest tag altogether. Question was not related to automatically monitoring changes in latest (what you propose, and in some cases that can be pretty involved script), but means to determine a correct version to make it fixed instead of simply set to latest (which can and will lead to surprises).