DockerCLI/cli/command/stack
Yong Tang 657457ee2c Use `scope=swarm` for service related network inspect.
This fix use `scope=swarm` for service related network inspect.
The purpose is that, in case multiple networks with the same
name exist in different scopes, it is still possible to obtain
the network for services.

This fix is related to moby/moby#33630 and docker/cli#167

Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
2017-06-13 20:26:12 +00:00
..
client_test.go Remove stack configs on stack removal 2017-05-26 18:17:43 -07:00
cmd.go Add interfacer linter 2017-05-08 15:57:50 -04:00
common.go Remove stack configs on stack removal 2017-05-26 18:17:43 -07:00
deploy.go Change --no-resolve-image flag to --resolve-image string flag 2017-06-07 12:30:11 -07:00
deploy_bundlefile.go Change --no-resolve-image flag to --resolve-image string flag 2017-06-07 12:30:11 -07:00
deploy_composefile.go Use `scope=swarm` for service related network inspect. 2017-06-13 20:26:12 +00:00
deploy_composefile_test.go Use `scope=swarm` for service related network inspect. 2017-06-13 20:26:12 +00:00
deploy_test.go Update imports. 2017-04-17 18:07:56 -04:00
list.go cli: gofmt + goimports 2017-05-08 10:51:30 -07:00
opts.go Update imports. 2017-04-17 18:07:56 -04:00
ps.go Update cli imports to using local package 2017-05-15 14:45:19 +02:00
remove.go Remove stack configs on stack removal 2017-05-26 18:17:43 -07:00
remove_test.go removed the output leaked from stack remove error test case 2017-06-09 12:14:18 -04:00
services.go Update cli imports to using local package 2017-05-15 14:45:19 +02:00