-
Notifications
You must be signed in to change notification settings - Fork 800
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
Support host configuration for docker-daemon sources and destinations #487
Conversation
Since you need to change containers/image, I changed your PR to a WIP. |
@rhatdan thanks, I've moved the vendor changes to containers/image#434 and unmarked the WIP |
1176a93
to
dd0e9ad
Compare
To support communication with docker daemons listening on plain HTTP only, this PR makes it possible to specify the scheme as part of the host URL, e.g. `http+tcp://localhost:2375` I'm not sure if this is a good idea - I needed a way to stop the httpClient from trying to use TLS, and this seemed like a reasonable approach, similar to how the python docker client behaves. Happy to discuss and iterate on this. Relates to containers/skopeo#487 Signed-off-by: Justin Lewis Salmon <[email protected]>
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.
Makes sense overall; please update docs/skopeo.1.md
and completions/bash/skopeo
as well.
AuthFilePath: c.String("authfile"), | ||
DockerDaemonHost: c.String(flagPrefix + "daemon-host"), | ||
DockerDaemonCertPath: c.String(flagPrefix + "cert-dir"), | ||
DockerDaemonInsecureSkipTLSVerify: !c.BoolT(flagPrefix + "tls-verify"), |
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 guess reusing the cert-dir
and tis-verify
flags to apply to docker-daemon:
as well makes sense—but their documentation throughout should be updated not to refer to “registries”.
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.
Good point. I've updated the docs to say "registry or daemon" - is that clear enough?
This PR makes it possible to communicate with docker daemons listening on plain HTTP only by specifying `http` as the url scheme e.g. `http://localhost:2375` Relates to containers/skopeo#487 Signed-off-by: Justin Lewis Salmon <[email protected]>
d4b34f7
to
228ff2d
Compare
Thanks @mtrmac for the review - I've updated the docs and completions as requested. |
ACK, pending containers/image#434 . |
@jlsalmon Can you do one final update, running |
I have updated the vendored copy of containers/image already, so please just rebase this. |
This PR adds CLI support for overriding the default docker daemon host when using the `docker-daemon` transport. Fixes containers#244 Signed-off-by: Justin Lewis Salmon <[email protected]>
228ff2d
to
0cea6dd
Compare
Rebased. Thanks guys! |
Thanks! |
This PR makes it possible to communicate with docker daemons listening on plain HTTP only by specifying `http` as the url scheme e.g. `http://localhost:2375` Relates to containers/skopeo#487 Signed-off-by: Justin Lewis Salmon <[email protected]>
This PR makes it possible to communicate with docker daemons listening on plain HTTP only by specifying `http` as the url scheme e.g. `http://localhost:2375` Relates to containers/skopeo#487 Signed-off-by: Justin Lewis Salmon <[email protected]>
This PR makes it possible to communicate with docker daemons listening on plain HTTP only by specifying `http` as the url scheme e.g. `http://localhost:2375` Relates to containers/skopeo#487 Signed-off-by: Justin Lewis Salmon <[email protected]>
This PR makes it possible to communicate with docker daemons listening on plain HTTP only by specifying `http` as the url scheme e.g. `http://localhost:2375` Relates to containers/skopeo#487 Signed-off-by: Justin Lewis Salmon <[email protected]>
This PR makes it possible to communicate with docker daemons listening on plain HTTP only by specifying `http` as the url scheme e.g. `http://localhost:2375` Relates to containers/skopeo#487 Signed-off-by: Justin Lewis Salmon <[email protected]>
This PR makes it possible to communicate with docker daemons listening on plain HTTP only by specifying `http` as the url scheme e.g. `http://localhost:2375` Relates to containers/skopeo#487 Signed-off-by: Justin Lewis Salmon <[email protected]>
This PR makes it possible to communicate with docker daemons listening on plain HTTP only by specifying `http` as the url scheme e.g. `http://localhost:2375` Relates to containers/skopeo#487 Signed-off-by: Justin Lewis Salmon <[email protected]>
This PR makes it possible to communicate with docker daemons listening on plain HTTP only by specifying `http` as the url scheme e.g. `http://localhost:2375` Relates to containers/skopeo#487 Signed-off-by: Justin Lewis Salmon <[email protected]>
This PR makes it possible to communicate with docker daemons listening on plain HTTP only by specifying `http` as the url scheme e.g. `http://localhost:2375` Relates to containers/skopeo#487 Signed-off-by: Justin Lewis Salmon <[email protected]>
This PR adds CLI support for overriding the default docker daemon host when using the
docker-daemon
transport.See also containers/image#434
Fixes #244
Signed-off-by: Justin Lewis Salmon [email protected]