failed to get tags from remote registry for "docker.elastic.co/beats/filebeat" about version-checker HOT 2 CLOSED

@duclm2609 Can you raise this as a separate issue if you're seeing UNAUTHENTICATED on ECR.

@yogeek - I'm assuming that this is a limitation at elastics end, many repository owners are preventing the searching of tags.

Whilst docker pull docker.elastic.co/beats/filebeat:7.10.2 is successful, the docker (or container run time for that matter) doesn't attempt to call the same API endpoints that version-checker needs to operate.

An example curl request results in the same effect:

$ curl https://docker.elastic.co/v2/beats/filebeat/tags/list
{"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"repository","Class":"","Name":"beats/filebeat","Action":"pull"}]}]}

I would suggest, attempting to setup the docker.elastic.co as a self-hosted registry with some credentials should allow you to track those image versions.

Unfortunately there's not an awful lot we can do from a project perspective on this.

from version-checker.

same issue with Docker image from AWS public ECR repository

from version-checker.