From f7b7d4470012fd6e760c83c6ef19c6036ea24bf0 Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Wed, 13 Mar 2019 17:33:57 -0700 Subject: [PATCH] Fix broken image links --- datacenter/ucp/3.0/guides/user/interlock/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/datacenter/ucp/3.0/guides/user/interlock/index.md b/datacenter/ucp/3.0/guides/user/interlock/index.md index cd63d61bfe..2deef44542 100644 --- a/datacenter/ucp/3.0/guides/user/interlock/index.md +++ b/datacenter/ucp/3.0/guides/user/interlock/index.md @@ -8,7 +8,7 @@ Docker Engine running in swarm mode has a routing mesh, which makes it easy to expose your services to the outside world. Since all nodes participate in the routing mesh, users can access your service by contacting any node. -![swarm routing mess](../images/interlock-overview-1.svg) +![swarm routing mess](../../images/interlock-overview-1.svg) In this example the WordPress service is listening on port 8000 of the routing mesh. Even though the service is running on a single node, users can access @@ -21,7 +21,7 @@ instead of IP addresses. This functionality is made available through the Interlock component. -![layer 7 routing](../images/interlock-overview-2.svg) +![layer 7 routing](../../images/interlock-overview-2.svg) In this example, users can access the WordPress service using `http://wordpress.example.org`. Interlock takes care of routing traffic to