Project

General

Profile

Bug #8873

need to handle non standalone registry auth for a docker pull call

Added by Partha Aji about 8 years ago. Updated about 8 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

PR https://github.com/theforeman/foreman-docker/pull/65 addresses the docker pull call for the standalone registries.
But we need to address cases involving non standalone registries, where we need to query the index for the location of the image, we also must use the authentication token that the index passes to us together with the response.
look at
https://docs.docker.com/reference/api/hub_registry_spec/#pull

for more info

History

#1 Updated by Dominic Cleal about 8 years ago

  • Project changed from Foreman to Docker
  • Category deleted (Authentication)

#2 Updated by Anonymous about 8 years ago

  • Status changed from New to Feedback

After looking at docker's remote api create image (docs + implementation), it became clear that docker service handles all interactions required for pulling of an image, including contacting the correct registry and handling of authentication tokens and endpoints.

I don't think we need to add support for token-based auth at this point.

Also available in: Atom PDF