Separate plugin sockets and specs.#13951
Conversation
17335be to
894f7e2
Compare
There was a problem hiding this comment.
maybe we should mention per plugin directory here with a specific example.
There was a problem hiding this comment.
@proppy that's define at the bottom of this section, like 42. Is that good enough?
|
Design LGTM |
|
@calavera What motivation behind separation unix sockets from specs? |
|
@LK4D4 I think that's more where people expect to find them. Unix sockets under /run, like other unix sockets and specs under a "configuration" directory. This is where we decided to go with this approach: |
|
okay |
There was a problem hiding this comment.
as I understand it, these changes leave the /usr/share path untested. is that accurate?
There was a problem hiding this comment.
the /usr/share path is completely gone, we are not going to make this stable with that path.
There was a problem hiding this comment.
ok, good to know.
On Jul 6, 2015, at 3:35 PM, David Calavera [email protected] wrote:
In integration-cli/docker_cli_start_volume_driver_unix_test.go #13951 (comment):
@@ -129,11 +129,11 @@ func (s *DockerExternalVolumeSuite) SetUpSuite(c *check.C) {
fmt.Fprintln(w,{})
})
- if err := os.MkdirAll("/usr/share/docker/plugins", 0755); err != nil {
- if err := os.MkdirAll("/etc/docker/plugins", 0755); err != nil {
the /usr/share path is completely gone, we are not going to make this stable with that path.—
Reply to this email directly or view it on GitHub https://github.com/docker/docker/pull/13951/files#r33990203.
|
LGTM other than the comments; but historically this stuff lives in /var/run -- is that a better place for it maybe? |
|
Any update on this PR? Without it I'm unable to test network plugins on CoreOS. And FWIW, I've been trying to test with this branch but I can't get it to work (with .sock files). I'm trying to create a network. i.e. The calico.sock file exists. Does this change require a corresponding change to libnetwork? |
|
@tomdee I made a small change but it doesn't look to be the error you get. I don't think networking requires anything special. Can you point me to your code? This is my gluster plugin being used with this PR: |
|
I've retested this and it's working fine with Calico (as a libnetwork remote plugin) now. Either your small change did it, or I had a permission problem on the /run/docker directory. I would love to see this merged ASAP - it would be great to start testing on CoreOS. (And FWIW - anyone wanting to do manual testing of this - |
|
LGTM |
There was a problem hiding this comment.
i know it's unrelated to this PR, but it's unfortunate we have another thing called Registry that has nothing to do with a docker registry :( we should consider renaming it to PluginService or PluginStore what do you think? Can be done in another PR, but just wanted to bring it to the attention
There was a problem hiding this comment.
yeah, I had the same feeling from the beginning, but naming is hard 😸
Let's think about something better somewhere else.
|
LGTM |
|
doc changes LGTM Keep in mind that this is an experimental feature; docs only need a "casual" review, but are not part of the official documentation, so it's mostly important to make sure that the information is correct |
There was a problem hiding this comment.
hm, thinking of this; perhaps you should mention in what order the directories are scanned, is that useful information?
There was a problem hiding this comment.
I added a short explanation about the scan ordering.
|
@thaJeztah the volume plugins are going in the 1.8 release. The docs will be moved to the right place after this lands on master. See #14659. |
Check if there is a plugin socket first under `/run/docker/plugins/NAME.sock`. If there is no socket for a plugin, check `/etc/docker/plugins/NAME.spec` and `/usr/lib/docker/plugins/NAME.spec` for spec files. Signed-off-by: David Calavera <[email protected]>
|
SGTM |
|
I'm a bit confused here.
Tentatively moving this to |
|
@icecrime IIUC, this not really touches the "docs" (as in, the docs here are still in the "experimental" directory). #14659 will promote this from "experimental" to "mainstream" and where the docs will be moved and touched-up to match the standards for the documentation. So yes, I think ready to merge is good. @calavera also pinged Mary to have a look, but I think that can be done on #14659. So I'll merge so we can proceed 👍 |
Separate plugin sockets and specs.
|
@calavera merged! |
Requires moby/moby#13951 Former-commit-id: ef6f0896168dc7fd7bd514652ce6a73f66f837ec
Check if there is a plugin socket first under
/run/docker/plugins/NAME.sock.If there is no socket for a plugin, check
/etc/docker/plugins/NAME.specand/usr/lib/docker/plugins/NAME.specfor spec files.Fixes #13859
/cc @lukemarsden
Signed-off-by: David Calavera [email protected]