Aaron Lehmann 161b2a50c3 cluster: Renew the context after communicating with the registry ... When pinning by digest, the registry might be slow or unresponsive. This could cause the context to already be expired by the time UpdateService or CreateService is called. We want digest pinning to be a best-effort operation, so it's problematic if a slow or misbehaving registry prevents the service operation from completing. Replace the context after communicating with the registry, so we have a fresh timeout for the gRPC call. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com> (cherry picked from commit f8273a216e)		2017-03-15 11:01:02 -07:00
..
convert	Change the way IPAM configuration is handled on stack deploy	2017-01-04 20:25:04 +01:00
executor	Fix issue where service healthcheck is {} in remote API	2017-03-13 21:21:19 -07:00
provider	Add engine-api types to docker	2016-09-07 11:05:58 -07:00
cluster.go	cluster: Renew the context after communicating with the registry	2017-03-15 11:01:02 -07:00
filters.go	secrets: secret management for swarm	2016-11-09 14:27:43 -05:00
helpers.go	fix changes for 1.13.x branch	2017-02-17 17:21:58 -08:00
listen_addr.go	Reject unspecified advertise addr on swarm init	2016-11-29 14:12:45 -08:00
listen_addr_linux.go	Add fallback to resolveSystemAddr() in linux	2016-09-09 13:27:57 -07:00
listen_addr_others.go	Add functional support for Docker sub commands on Solaris	2016-11-07 09:06:34 -08:00
listen_addr_solaris.go	Add functional support for Docker sub commands on Solaris	2016-11-07 09:06:34 -08:00
secrets.go	judge manager before getting secret	2016-11-14 11:54:29 -08:00