these markdown files are not consumed directly in the docs, but only their content is included through the YAML does, so there's no need to have these comments in them Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
1.5 KiB
1.5 KiB
title, description, keywords
title | description | keywords |
---|---|---|
plugin create | the plugin create command description and usage | plugin, create |
plugin create
Usage: docker plugin create [OPTIONS] PLUGIN PLUGIN-DATA-DIR
Create a plugin from a rootfs and configuration. Plugin data directory must contain config.json and rootfs directory.
Options:
--compress Compress the context using gzip
--help Print usage
Description
Creates a plugin. Before creating the plugin, prepare the plugin's root filesystem as well as the config.json
Examples
The following example shows how to create a sample plugin
.
$ ls -ls /home/pluginDir
total 4
4 -rw-r--r-- 1 root root 431 Nov 7 01:40 config.json
0 drwxr-xr-x 19 root root 420 Nov 7 01:40 rootfs
$ docker plugin create plugin /home/pluginDir
plugin
$ docker plugin ls
ID NAME TAG DESCRIPTION ENABLED
672d8144ec02 plugin latest A sample plugin for Docker false
The plugin can subsequently be enabled for local use or pushed to the public registry.