From 4291e391bddb392a0705b6e1ea3cf42fef155804 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Thu, 21 Jan 2021 15:58:03 +0100 Subject: [PATCH] fix broken links in "working with contexts" Signed-off-by: Sebastiaan van Stijn --- engine/context/working-with-contexts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/engine/context/working-with-contexts.md b/engine/context/working-with-contexts.md index c32c34716f..65d17f59ff 100644 --- a/engine/context/working-with-contexts.md +++ b/engine/context/working-with-contexts.md @@ -13,7 +13,7 @@ A single Docker CLI can have multiple contexts. Each context contains all of the As an example, a single Docker client on your company laptop might be configured with two contexts; **dev-k8s** and **prod-swarm**. **dev-k8s** contains the endpoint data and security credentials to configure and manage a Kubernetes cluster in a development environment. **prod-swarm** contains everything required to manage a Swarm cluster in a production environment. Once these contexts are configured, you can use the top-level `docker context use ` to easily switch between them. -For information on using Docker Context to deploy your apps to the cloud, see [Deploying Docker containers on Azure](aci-integration.md) and [Deploying Docker containers on ECS](ecs-integration.md). +For information on using Docker Context to deploy your apps to the cloud, see [Deploying Docker containers on Azure](../../cloud/aci-integration.md) and [Deploying Docker containers on ECS](../../cloud/ecs-integration.md). ## Prerequisites