-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Refactoring of DockerClientConfig #447
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -85,56 +85,62 @@ For code examples, please look at the [Wiki](https://github.com/docker-java/dock | |
|
|
||
| There are a couple of configuration items, all of which have sensible defaults: | ||
|
|
||
| * `url` The Docker URL, e.g. `https://localhost:2376` or `unix:///var/run/docker.sock` | ||
| * `version` The API version, e.g. `1.16`. | ||
| * `username` Your registry username (required to push containers). | ||
| * `password` Your registry password. | ||
| * `email` Your registry email. | ||
| * `serverAddress` Your registry's address. | ||
| * `dockerCertPath` Path to the docker certs. | ||
| * `DOCKER_HOST` The Docker Host URL, e.g. `tcp://localhost:2376` or `unix:///var/run/docker.sock` | ||
| * `DOCKER_TLS_VERIFY` enable/disable TLS verification (switch between `http` and `https` protocol) | ||
| * `DOCKER_CERT_PATH` Path to the certificates needed for TLS verification | ||
| * `DOCKER_CONFIG` Path for additional docker configuration files (like `.dockercfg`) | ||
| * `api.version` The API version, e.g. `1.21`. | ||
| * `registry.url` Your registry's address. | ||
| * `registry.username` Your registry username (required to push containers). | ||
| * `registry.password` Your registry password. | ||
| * `registry.email` Your registry email. | ||
|
|
||
| There are three ways to configure, in descending order of precedence: | ||
|
|
||
| #### Programmatic: | ||
| In your application, e.g. | ||
|
|
||
| DockerClientConfig config = DockerClientConfig.createDefaultConfigBuilder() | ||
| .withVersion("1.16") | ||
| .withUri("https://my-docker-host.tld:2376") | ||
| .withUsername("dockeruser") | ||
| .withPassword("ilovedocker") | ||
| .withEmail("[email protected]") | ||
| .withServerAddress("https://index.docker.io/v1/") | ||
| .withDockerCertPath("/home/user/.docker") | ||
| .withDockerHost("tcp://my-docker-host.tld:2376") | ||
| .withDockerTlsVerify(true) | ||
| .withDockerCertPath("/home/user/.docker/certs") | ||
| .withDockerConfig("/home/user/.docker") | ||
| .withApiVersion("1.21") | ||
| .withRegistryUrl("https://index.docker.io/v1/") | ||
| .withRegistryUsername("dockeruser") | ||
| .withRegistryPassword("ilovedocker") | ||
| .withRegistryEmail("[email protected]") | ||
| .build(); | ||
| DockerClient docker = DockerClientBuilder.getInstance(config).build(); | ||
|
|
||
| #### Properties | ||
|
|
||
| docker.io.url=https://localhost:2376 | ||
| docker.io.version=1.16 | ||
| docker.io.username=dockeruser | ||
| docker.io.password=ilovedocker | ||
| [email protected] | ||
| docker.io.serverAddress=https://index.docker.io/v1/ | ||
| docker.io.dockerCertPath=/home/user/.docker | ||
| #### Properties (docker-java.properties) | ||
|
|
||
| DOCKER_HOST=tcp://localhost:2376 | ||
| DOCKER_TLS_VERIFY=1 | ||
| DOCKER_CERT_PATH=/home/user/.docker/certs | ||
| DOCKER_CONFIG=/home/user/.docker | ||
| api.version=1.21 | ||
| registry.url=https://index.docker.io/v1/ | ||
| registry.username=dockeruser | ||
| registry.password=ilovedocker | ||
| [email protected] | ||
|
|
||
| ##### System Properties: | ||
|
|
||
| java -Ddocker.io.username=dockeruser pkg.Main | ||
| java -Dregistry.username=dockeruser pkg.Main | ||
|
|
||
| ##### System Environment | ||
|
|
||
| export DOCKER_URL=http://localhost:2376 | ||
|
|
||
| Note: we also auto-detect defaults. If you use `DOCKER_HOST` we use that value, and if `DOCKER_CERT_PATH` or `DOCKER_TLS_VERIFY=1` is set, we switch to SSL. | ||
| export DOCKER_URL=tcp://localhost:2376 | ||
| export DOCKER_TLS_VERIFY=1 | ||
| export DOCKER_CERT_PATH=/home/user/.docker/certs | ||
| export DOCKER_CONFIG=/home/user/.docker | ||
|
|
||
| ##### File System | ||
|
|
||
| In `$HOME/.docker.io.properties` | ||
| In `$HOME/.docker-java.properties` | ||
|
|
||
| ##### Class Path | ||
|
|
||
| In the class path at `/docker.io.properties` | ||
| In the class path at `/docker-java.properties` | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you need registry related things in client initialisation?
I.e. if you have 2 auth registries you should call auth cmd and only then push.
I also not sure what will happen with parallel pushes...
PS. found, pull/push supports optional auth methods.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw, how AuthCmd should work?
With uncommented lines fails because
authCmd()checks for username+server:And it impossible to set new auth with later command.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think credentials in config originated from times when only docker hub was there and no private registries existed. So currently you can think of it as a default credential. There is an open issue #316 that is related to a refactoring of the auth configurations also. IMHO these authentication issues are out of scope of this PR and should be fixed in a separate one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, 🏧 developing ability to specify credentials for pull/push images for jenkins plugin and decided to ask during refactoring.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#452