mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
342ed107bc
Embedding DockerVersion in plugin config when the plugin is created, enables users to do a docker plugin inspect and know which version the plugin was built on. This is helpful in cases where users are running a new plugin on older docker releases and confused at unexpected behavior. By embedding DockerVersion in the config, we claim that there's no guarantee that if the plugin config's DockerVersion is greater that the version of the docker engine the plugin is executed against, the plugin will work as expected. For example, lets say: - in 17.03, a plugin was released as johndoe/foo:v1 - in 17.05, the plugin uses the new ipchost config setting and author publishes johndoe/foo:v2 In this case, johndoe/foo:v2 was built on 17.05 using ipchost, but is running on docker-engine version 17.03. Since 17.05 > 17.03, there's no guarantee that the plugin will work as expected. Ofcourse, if the plugin did not use newly added config settings (ipchost in this case) in 17.05, it would work fine in 17.03. Signed-off-by: Anusha Ragunathan <anusha.ragunathan@docker.com> |
||
|---|---|---|
| .. | ||
| backend | ||
| blkiodev | ||
| container | ||
| events | ||
| filters | ||
| image | ||
| mount | ||
| network | ||
| registry | ||
| strslice | ||
| swarm | ||
| time | ||
| versions | ||
| volume | ||
| auth.go | ||
| client.go | ||
| configs.go | ||
| error_response.go | ||
| graph_driver_data.go | ||
| id_response.go | ||
| image_delete_response_item.go | ||
| image_summary.go | ||
| plugin.go | ||
| plugin_device.go | ||
| plugin_env.go | ||
| plugin_interface_type.go | ||
| plugin_mount.go | ||
| plugin_responses.go | ||
| port.go | ||
| seccomp.go | ||
| service_update_response.go | ||
| stats.go | ||
| types.go | ||
| volume.go | ||