Context/path based routing

Estimated reading time: 1 minute

In this example we will publish a service using context or path based routing.

First we will create an overlay network so that service traffic is isolated and secure:

$> docker network create -d overlay demo

Next we will create the initial service:

$> docker service create \
    --name demo \
    --network demo \
    --detach=false \
    --label \
    --label \
    --label \
    --label \
    --env METADATA="demo-context-root" \

Only one path per host

Interlock supports only one path per host per service cluster. Once a particular label has been applied, it cannot be applied again in the same service cluster.

Interlock will detect once the service is available and publish it. Once the tasks are running and the proxy service has been updated the application should be available via http://demo.local:

$> curl -vs -H "Host: demo.local"
*   Trying
* Connected to ( port 80 (#0)
> GET /app/ HTTP/1.1
> Host: demo.local
> User-Agent: curl/7.54.0
> Accept: */*
< HTTP/1.1 200 OK
< Server: nginx/1.13.6
< Date: Fri, 17 Nov 2017 14:25:17 GMT
< Content-Type: text/html; charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< x-request-id: 077d18b67831519defca158e6f009f82
< x-proxy-id: 77c0c37d2c46
< x-server-info: interlock/2.0.0-dev (732c77e7) linux/amd64
< x-upstream-addr:
< x-upstream-response-time: 1510928717.306
routing, proxy