Push a plugin to a registry
API 1.25+ The client and daemon API must both be at least 1.25 to use this command. Use the docker version command on the client to check your client and daemon API versions.
docker plugin push [OPTIONS] PLUGIN[:TAG]
| Name, shorthand | Default | Description |
--disable-content-trust | true | Skip image signing |
| Command | Description |
|---|---|
| docker plugin | Manage plugins |
| Command | Description |
| docker plugin create | Create a plugin from a rootfs and configuration. Plugin data directory must contain config.json and rootfs directory. |
| docker plugin disable | Disable a plugin |
| docker plugin enable | Enable a plugin |
| docker plugin inspect | Display detailed information on one or more plugins |
| docker plugin install | Install a plugin |
| docker plugin ls | List plugins |
| docker plugin push | Push a plugin to a registry |
| docker plugin rm | Remove one or more plugins |
| docker plugin set | Change settings for a plugin |
| docker plugin upgrade | Upgrade an existing plugin |
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.
Registry credentials are managed by docker login.
The following example shows how to push a sample user/plugin.
$ docker plugin ls
ID NAME TAG DESCRIPTION ENABLED
69553ca1d456 user/plugin latest A sample plugin for Docker false
$ docker plugin push user/plugin
© 2019 Docker, Inc.
Licensed under the Apache License, Version 2.0.
Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries.
Docker, Inc. and other parties may also have trademark rights in other terms used herein.
https://docs.docker.com/engine/reference/commandline/plugin_push/