From 278b2ca0bc98f4679bd79bac8b5d7727263212c0 Mon Sep 17 00:00:00 2001 From: paigehargrave Date: Mon, 11 Mar 2019 16:51:50 -0400 Subject: [PATCH] Moved to interlock-vip info --- ee/ucp/interlock/usage/default-backend.md | 37 ----------------------- 1 file changed, 37 deletions(-) delete mode 100644 ee/ucp/interlock/usage/default-backend.md diff --git a/ee/ucp/interlock/usage/default-backend.md b/ee/ucp/interlock/usage/default-backend.md deleted file mode 100644 index dfe5129d1b..0000000000 --- a/ee/ucp/interlock/usage/default-backend.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Default host -description: Learn how to publish a service to be a default host. -keywords: routing, proxy ---- - -# Publishing a default host service - -The following example publishes a service to be a default host. The service responds -whenever there is a request to a host that is not configured. - -First, create an overlay network so that service traffic is isolated and secure: - -```bash -$> docker network create -d overlay demo -1se1glh749q1i4pw0kf26mfx5 -``` - -Next, create the initial service: - -```bash -$> docker service create \ - --name demo-default \ - --network demo \ - --detach=false \ - --replicas=1 \ - --label com.docker.lb.default_backend=true \ - --label com.docker.lb.port=8080 \ - ehazlett/interlock-default-app -``` - -Interlock detects when the service is available and publishes it. After tasks are running -and the proxy service is updated, the application is available via any url that is not -configured: - - -![Default Backend](../../images/interlock_default_backend.png)