Skip to content
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

Merged
merged 1 commit into from
Apr 7, 2018

Conversation

jlsalmon
Copy link
Contributor

@jlsalmon jlsalmon commented Mar 30, 2018

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]

@rhatdan rhatdan changed the title Support host configuration for docker-daemon sources and destinations [WIP] Support host configuration for docker-daemon sources and destinations Mar 30, 2018
@rhatdan
Copy link
Member

rhatdan commented Mar 30, 2018

Since you need to change containers/image, I changed your PR to a WIP.

@rhatdan
Copy link
Member

rhatdan commented Apr 2, 2018

@runcom @mtrmac PTAL

@jlsalmon jlsalmon changed the title [WIP] Support host configuration for docker-daemon sources and destinations Support host configuration for docker-daemon sources and destinations Apr 3, 2018
@jlsalmon
Copy link
Contributor Author

jlsalmon commented Apr 3, 2018

@rhatdan thanks, I've moved the vendor changes to containers/image#434 and unmarked the WIP

@jlsalmon jlsalmon force-pushed the configure-daemon-host branch from 1176a93 to dd0e9ad Compare April 3, 2018 10:52
jlsalmon added a commit to jlsalmon/image that referenced this pull request Apr 3, 2018
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]>
Copy link
Contributor

@mtrmac mtrmac left a 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"),
Copy link
Contributor

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”.

Copy link
Contributor Author

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?

jlsalmon added a commit to jlsalmon/image that referenced this pull request Apr 4, 2018
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]>
@jlsalmon jlsalmon force-pushed the configure-daemon-host branch 3 times, most recently from d4b34f7 to 228ff2d Compare April 4, 2018 10:31
@jlsalmon
Copy link
Contributor Author

jlsalmon commented Apr 4, 2018

Thanks @mtrmac for the review - I've updated the docs and completions as requested.

@mtrmac
Copy link
Contributor

mtrmac commented Apr 5, 2018

ACK, pending containers/image#434 .

@mtrmac
Copy link
Contributor

mtrmac commented Apr 5, 2018

@jlsalmon Can you do one final update, running vndr in the skopeo directory, and adding the vendor updates to this PR, please?

@mtrmac
Copy link
Contributor

mtrmac commented Apr 5, 2018

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]>
@jlsalmon jlsalmon force-pushed the configure-daemon-host branch from 228ff2d to 0cea6dd Compare April 7, 2018 04:15
@jlsalmon
Copy link
Contributor Author

jlsalmon commented Apr 7, 2018

Rebased. Thanks guys!

@mtrmac
Copy link
Contributor

mtrmac commented Apr 7, 2018

Thanks!

@mtrmac mtrmac merged commit 28080c8 into containers:master Apr 7, 2018
@jlsalmon jlsalmon deleted the configure-daemon-host branch April 7, 2018 04:29
Jamesjaj2dc6j added a commit to Jamesjaj2dc6j/lucascalsilvaa that referenced this pull request Jun 6, 2022
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]>
mrhyperbit23z0d added a commit to mrhyperbit23z0d/thomasdarimont that referenced this pull request Jun 6, 2022
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]>
easyriderk0c9g added a commit to easyriderk0c9g/rnin9 that referenced this pull request Jun 6, 2022
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]>
oguzturker8ijm8l added a commit to oguzturker8ijm8l/diwir that referenced this pull request Jun 6, 2022
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]>
wesnowm added a commit to wesnowm/MatfOOP- that referenced this pull request Jun 6, 2022
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]>
gaveen3 added a commit to gaveen3/KimJeongHoon3x that referenced this pull request Jun 6, 2022
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]>
gaveen3 added a commit to gaveen3/KimJeongHoon3x that referenced this pull request Jun 6, 2022
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]>
Manuel-Suarez-Abascal80n9y added a commit to Manuel-Suarez-Abascal80n9y/knimeu that referenced this pull request Oct 7, 2022
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]>
straiforos8bsh5n added a commit to straiforos8bsh5n/tokingsq that referenced this pull request Oct 7, 2022
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]>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants