Skip to content

Add plugin dev doc to TOC #263

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 1 commit into from
Oct 20, 2016
Merged

Add plugin dev doc to TOC #263

merged 1 commit into from
Oct 20, 2016

Conversation

mdlinville
Copy link

Describe the proposed changes

Add link to the TOC
While I'm at it, test and update the content for clarity (several commands needed sudo, for instance)

Project version

n/a

Related issue

#252

Please take a look

@icecrime @vieux @thaJeztah

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left some comments, but nice improvement overall!


## How to operate a plugin
To install a plugin, use the `docker plugin install` command, which pulls the
plugin from the the configured registry, prompts you to grant permissions if
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/the the/the/

not sure about "configured registry", as the plugins reference determines which registry to use (e.g. myregistry:5000/my/plugin:latest). Perhaps just "registry" (or "Docker Hub")

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

```

5. Verify the plugin successfully created the volume.
5. Use the volume `sshvolume` to start a container.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Almost reads as "the volume starts the container" 🐰

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I misunderstood this the first time around. Fixed.

2. Create manifest.json file in `/var/lib/docker/plugins/$id/`.
3. Create a `plugin-config.json` if needed.
4. Create or add a section to `/var/lib/docker/plugins/plugins.json`. Use
2. Create a `rootfs` and export it to `/var/lib/docker/plugins/$id/rootfs`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what is meant by "export it to" here

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added some explanation and a pointer to the example higher up in the file.

@johndmulhausen
Copy link

Looks good from a docs perspective; once @thaJeztah 's comments are addressed, merge away!

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spotted two typos, but content LGTM

however, I just realized we marked this directory as "not edit here"; https://github.com/docker/docker.github.io/blob/master/.NOT_EDITED_HERE.txt#L24 😅

@@ -78,6 +69,8 @@ started without error.
```

3. Create a volume using the plugin.
This example mounts the `/remmote` directory on host `1.2.3.4` into a
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo; remmote

@@ -78,6 +69,8 @@ started without error.
```

3. Create a volume using the plugin.
This example mounts the `/remmote` directory on host `1.2.3.4` into a
volume nammed `sshvolume`. This volume can now be mounted into containers.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo nammed

@johndmulhausen
Copy link

Can I ask why /engine/extend/ wouldn't live in the docs repo? It is clearly a handwritten tutorial and not something that would ever be auto-generated, and not any more release-bound than any other writer-curated content that could be tracked in vnext-engine

https://docker.github.io/engine/extend/

@thaJeztah
Copy link
Member

@johndmulhausen because a large part of it is "reference", which is tightly coupled to code changes, also there's a manifest in there, that should not be separated from the code.

We may consider moving those parts underneath "reference" (plugin-api, plugin manifest?)

Fixes #252

Signed-off-by: Misty Stanley-Jones <[email protected]>
@mdlinville mdlinville changed the title Improve plugin dev doc and add to TOC Add plugin dev doc to TOC Oct 20, 2016
@mdlinville
Copy link
Author

Moved the rewrite section of the PR to moby/moby#27593

@mdlinville mdlinville merged commit d24399b into docker:master Oct 20, 2016
@mdlinville mdlinville deleted the 252_add_managed_plugin_toc branch October 20, 2016 18:19
@johndmulhausen
Copy link

@thaJeztah Fair enough. Currently, NOT_EDITED_HERE.txt is marking all of /engine/extend/ as "not edited here" -- is it just index.md, or is it really the whole directory?

@mdlinville
Copy link
Author

I'll split this up and only keep the menu part here, move the edits to
docker/docker. Thanks for the reminder. I can't wait for this to be
automated!

On Thu, Oct 20, 2016 at 10:49 AM, Sebastiaan van Stijn <
[email protected]> wrote:

@johndmulhausen https://github.com/johndmulhausen because a large part
of it is "reference", which is tightly coupled to code changes, also
there's a manifest in there, that should not be separated from the code.

We may consider moving those parts underneath "reference" (plugin-api,
plugin manifest?)


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#263 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHUa9Wy3HlgbUdRylp4gxFCTfEFpDYbbks5q16mfgaJpZM4KaXXC
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants