DockerHub not updating repository timestamp when updated repo pushed with same tag

When I push an updated Docker image to DockerHub using the same repository name and tag (version number), the new layers appear to be uploaded to DockerHub, and my DockerHub UI main page indicates the repository with that name was updated “nn minutes ago”.

But when I select that repository and the UI transitions to the page for that repository, the UI indicates “Updated 1 week, 4 days ago” and under Properties, the original date still appears.

  • How to mask multiple Docker containers to a single public IP on Windows 10/ Server 2016
  • Restart failed Selenium browser
  • Kubernetes - Unknown admission plugin: DefaultStorageClass
  • Docker downloaded over 30 ubuntu images
  • change ip address for docker
  • HaProxy + docker health-checks restart dead containers
  • Shouldn’t the timestamp information on this page reflect the latest update?

  • When docker run, an error occurs. “ValueError: Unable to configure handler 'watchtower': You must specify a region.”
  • 'docker-compose up' inside project folder returns 'no such file or directory'
  • How to delete untagged images from AWS ECR Container Registry
  • How to prevent RabbitMQ settings to be lost during intermediate steps of a Dockerfile?
  • Vagrant managed docker container doesn't start
  • Makefile hangs when docker-compose -d is used and fails with code 129 without -d
  • One Solution collect form web for “DockerHub not updating repository timestamp when updated repo pushed with same tag”

    I posted this same question to the Docker Forum just now and received the following reply:

    We should definitely have better “updated” information. I’ll check to see if I can find out why that elapsed time in the upper right corner is so off from the last push.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.