-
Notifications
You must be signed in to change notification settings - Fork 640
-
Notifications
You must be signed in to change notification settings - Fork 640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configure registry auth token or take it from ~/.dockercfg #147
Comments
this would be a good enhancement but i think we should wait to see how this moby/moby#12009 shakes out before we do anything w/ it given we will have to decide if we want to be backwards compatible. |
I think, that's also a good idea. One could add it to the lookup chain for the credentials, that we already have:
|
docker now stores this in newer versions in |
A similar fallback should happen when pushing to a OpenShift registry, where |
Would be also cool to check for the timestap of the configuration files examined to decided which one to check first. |
Currently the plugin is using the auth also for pulling images when doing a build, and does this by extracting the username from the image to pull. This is obviously completely bogus, so we should change this to completely ignore the authentication for pulling. All at least ignore the usual configurations (system props, settings.xml) for authentication and only examine the docker config or openshift config. See also fabric8io/fabric8-devops#46 |
Here's where the auth configuration is used for pulling (and where it extracts the username for the pull); https://github.com/rhuss/docker-maven-plugin/blob/d7a4ca8a90f0bddaaf71581a8642913c9b0ae19b/src/main/java/org/jolokia/docker/maven/AbstractDockerMojo.java#L386 An option could be also to include a global variable like |
If a default login for the registry is configured for authentication this will be used, regardless of the image's username. If no default login is registered, no authentication is used. This affects only pulling. For push, the default user is extracted from the image name (but can be overwritten with options and config). This also will fix fabric8io/fabric8-devops#46 Relates to #147
Implemented lookup of credentials within For the fined grained authentication with pull vs. push and the Kubernetes support in |
Follup issues created, so that this can be closed now. |
Would it be possible to get the auth token and send it with the X-Registry-Auth header instead of using plain username/password authentication?
As the docker host and cert path this should be configurable in maven or by default pick the default location from the filesystem (~/.dockercfg in this case)
The text was updated successfully, but these errors were encountered: