Guest24897
/
DockerCLI
mirror of https://github.com/docker/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
DockerCLI/docs/reference/commandline/plugin_push.md

47 lines
1.2 KiB
Markdown
Raw Normal View History

docs: generate markdown Keep frontmatter for docker, dockerd and index markdown files. Also needs to move cli.md > docker.md before generation and then move it back because cli.md is needed for yaml generation on docs website: https://github.com/docker/cli/pull/3924#discussion_r1059986605 Signed-off-by: Kevin Alvarez <crazy-max@users.noreply.github.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-01-06 13:04:05 -05:00
# plugin push
Add docs for plugin push Signed-off-by: Anusha Ragunathan <anusha@docker.com>
2016-11-14 11:38:06 -05:00
docs: generate markdown Keep frontmatter for docker, dockerd and index markdown files. Also needs to move cli.md > docker.md before generation and then move it back because cli.md is needed for yaml generation on docs website: https://github.com/docker/cli/pull/3924#discussion_r1059986605 Signed-off-by: Kevin Alvarez <crazy-max@users.noreply.github.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-01-06 13:04:05 -05:00
<!---MARKER_GEN_START-->
Add docs for plugin push Signed-off-by: Anusha Ragunathan <anusha@docker.com>
2016-11-14 11:38:06 -05:00
Push a plugin to a registry
docs: generate markdown Keep frontmatter for docker, dockerd and index markdown files. Also needs to move cli.md > docker.md before generation and then move it back because cli.md is needed for yaml generation on docs website: https://github.com/docker/cli/pull/3924#discussion_r1059986605 Signed-off-by: Kevin Alvarez <crazy-max@users.noreply.github.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-01-06 13:04:05 -05:00
### Options
docs: regenerate markdown Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2024-02-21 03:51:39 -05:00
| Name | Type | Default | Description |
|:--------------------------|:-------|:--------|:-------------------|
| `--disable-content-trust` | `bool` | `true` | Skip image signing |
docs: generate markdown Keep frontmatter for docker, dockerd and index markdown files. Also needs to move cli.md > docker.md before generation and then move it back because cli.md is needed for yaml generation on docs website: https://github.com/docker/cli/pull/3924#discussion_r1059986605 Signed-off-by: Kevin Alvarez <crazy-max@users.noreply.github.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-01-06 13:04:05 -05:00
<!---MARKER_GEN_END-->
Add docs for plugin push Signed-off-by: Anusha Ragunathan <anusha@docker.com>
2016-11-14 11:38:06 -05:00
Standardized formatting of CLI reference commands Command name should be a H1 Only Description, Examples, and Related Commands should be H2 Changed 'Related information' heading to 'Related commands' since 99% it is only linking commands Added some examples where relevant Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2017-02-07 18:42:48 -05:00
## Description
After you have created a plugin using `docker plugin create` and the plugin is
ready for distribution, use `docker plugin push` to share your images to Docker
Hub or a self-hosted registry.
Add docs for plugin push Signed-off-by: Anusha Ragunathan <anusha@docker.com>
2016-11-14 11:38:06 -05:00
Registry credentials are managed by [docker login](login.md).
Standardized formatting of CLI reference commands Command name should be a H1 Only Description, Examples, and Related Commands should be H2 Changed 'Related information' heading to 'Related commands' since 99% it is only linking commands Added some examples where relevant Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2017-02-07 18:42:48 -05:00
## Examples
Add docs for plugin push Signed-off-by: Anusha Ragunathan <anusha@docker.com>
2016-11-14 11:38:06 -05:00
The following example shows how to push a sample `user/plugin`.
docs: use "console" code-hint for shell examples This replaces the use of bash where suitable, to allow easier copy/pasting of shell examples without copying the prompt or process output. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-08-21 08:54:14 -04:00
```console
Add docs for plugin push Signed-off-by: Anusha Ragunathan <anusha@docker.com>
2016-11-14 11:38:06 -05:00
$ docker plugin ls
Standardized formatting of CLI reference commands Command name should be a H1 Only Description, Examples, and Related Commands should be H2 Changed 'Related information' heading to 'Related commands' since 99% it is only linking commands Added some examples where relevant Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2017-02-07 18:42:48 -05:00
docs: fix example output for docker plugin ls The output format was changed to combine tag and name in a single column, but this change was never reflected in the docs. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-06-18 10:37:36 -04:00
ID NAME DESCRIPTION ENABLED
69553ca1d456 user/plugin:latest A sample plugin for Docker false
fix some typos for plugin Signed-off-by: yuexiao-wang <wang.yuexiao@zte.com.cn>
2017-04-27 17:24:49 -04:00
Add docs for plugin push Signed-off-by: Anusha Ragunathan <anusha@docker.com>
2016-11-14 11:38:06 -05:00
$ docker plugin push user/plugin
```
Standardized formatting of CLI reference commands Command name should be a H1 Only Description, Examples, and Related Commands should be H2 Changed 'Related information' heading to 'Related commands' since 99% it is only linking commands Added some examples where relevant Signed-off-by: Misty Stanley-Jones <misty@docker.com>
2017-02-07 18:42:48 -05:00
## Related commands
Add docs for plugin push Signed-off-by: Anusha Ragunathan <anusha@docker.com>
2016-11-14 11:38:06 -05:00
* [plugin create](plugin_create.md)
* [plugin disable](plugin_disable.md)
* [plugin enable](plugin_enable.md)
* [plugin inspect](plugin_inspect.md)
* [plugin install](plugin_install.md)
* [plugin ls](plugin_ls.md)
* [plugin rm](plugin_rm.md)
* [plugin set](plugin_set.md)
Add docker plugin upgrade This allows a plugin to be upgraded without requiring to uninstall/reinstall a plugin. Since plugin resources (e.g. volumes) are tied to a plugin ID, this is important to ensure resources aren't lost. The plugin must be disabled while upgrading (errors out if enabled). This does not add any convenience flags for automatically disabling/re-enabling the plugin during before/after upgrade. Since an upgrade may change requested permissions, the user is required to accept permissions just like `docker plugin install`. Signed-off-by: Brian Goff <cpuguy83@gmail.com>
2017-01-28 19:54:32 -05:00
* [plugin upgrade](plugin_upgrade.md)