Problem getting Alpine tags programatically - "410 Gone" error

General
1

My team builds a couple of Alpine images based on the latest and next-most-recent versions and use a command like the following in our automation script to discovery the current tags:

$ curl -s https://registry.hub.docker.com/v1/repositories/alpine/tags | head
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   140  100   140    0     0    897      0 --:--:-- --:--:-- --:--:--   891
<html>
<head><title>410 Gone</title></head>
<body>
<center><h1>410 Gone</h1></center>
<hr><center>openresty</center>
</body>
</html>
$

I don’t have an example of how this is supposed to look but it’s not working presently. Our build process runs at least once a day and I know this has been working. This is a similar technique used in How can I list all tags for a Docker image on a remote registry?

What’s wrong? Will the command work soon? Is there an alternative command? Is there a better place to contact about this issue?

2

The StackOverflow post I mentioned suggested a registry v2 API that seems to work:

$ curl -L -s 'https://registry.hub.docker.com/v2/repositories/library/alpine/tags?page_size=1024' | jq '."results"[]["name"]' | tr -d \" | sort -V | grep -E "^[0-9]+[.][0-9]+$" | tail -1
3.16
$

Is the v1 method deprecated?

3

If the HTTP response is 410 Gone, it is not deprecated, it is discontinued (at least the endpoint you tried to use). For me, deprecation means it still works, but you should not use it.

However, Docker posted a blog post some days ago about the deprecations:

mentioning that some endpoints would give us 404 status code. It is 410, but yes, v1 will no longer work.