Apologies for the inconvenience! Let me provide some context here and hopefully clear some things up.
We are slowly migrating our Docker Hub convenience images from manual to automated build repositories.
The benefits of automated builds are that we get integrated/automated Docker Hub support for Dockerfiles and READMEs.
So, for example, our Android repository now has a full description, which was automatically pulled from a GitHub repository, along with an example Dockerfile, so you can see exactly how these images are built.
We are making these changes to provide better visibility into and transparency around our convenience images—a top customer request for a number of months now.
Unfortunately, because, believe it or not, it is impossible to rename a Docker Hub repository, and impossible to convert a regular repository to an automated build repository, this process involved deleting and recreating the repository on Docker Hub.
We have been doing this successfully, without losing any of our images, by pulling all variants of a particular image into a long-running CircleCI job, then deleting and recreating the repository on Docker Hub, then pushing all variants back up to that new automated build repository.
@mayu you managed to catch us during the few minutes of downtime while this migration process was occurring… In the future, we will be working to ensure that these migrations occur during times when there is as little usage of these images as possible. Zero downtime is probably impossible, but we will work to come as close to zero as we can. And in the long run, the usability of these images will be greatly increased after these migrations.
@halfer unfortunately, as you say, pinning the
sha256 of a specific variant doesn’t quite work here, as, when the images are deleted and re-pushed, they have new SHAs.
That said, in the case of the Android images, all the tags were restored shortly after your original post @mayu.
The PHP images are a separate concern @aautar @alvarollmenezes @bdwilliams @gedex… As you can see from Docker Hub, we have not migrated PHP to an automated build repository yet…
We are not sure why some tags are causing errors for folks, but we believe this is a Docker Hub issue and we are investigating. We are also working to re-build and re-push all old PHP tags, just in case—that work should be done in the next day or two.
Finally, just as a heads-up about what is coming down the line from CircleCI, we are working towards disentangling ourselves a bit from our dependency on Docker Hub, so that these kinds of issues do not impact end users in the future. We’ll keep you updated as to what that solution will look like!
And for future reference, we will be using the #convenience-images tag on Discuss to post relevant announcements about future changes to images.
Thanks everyone for your questions and concerns!