Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-7658

Confusing logs when docker registry lookup fails

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: 4.1.0
    • Fix Version/s: 4.2.0
    • Component/s: Docker
    • Labels:
      None

      Description

      The logs generated when a docker remote fails are not as useful as they could be. When you do a pull you get a log similar to:

      2015-07-10 22:03:29,583 [http-bio-8081-exec-10] [INFO ] (o.a.a.d.r.v.DockerV2RemoteRepoHandler:149) - Fetching docker manifest for repo 'testing/testing' and tag 'latest'

      There's a few issues with this
      1) It's identical when we've already got the image cached and when the manifest fails to be retrieved.
      2) If it fails there's no indication why the failure happened, you should be able to tell if it was an authorization failure or the artifact was not actually there.
      3) Which repository is being access is not printed, only the artifact. If you had the same artifact in two repositories there would be no way to tell which one it came from in the access log. You can see it in the request log however.

        Attachments

          Activity

            People

            • Assignee:
              freds Fred Simon
              Reporter:
              denebeim Jay Denebeim (Inactive)
              Assigned QA:
              Matan Katz
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: