docker/docs
1
0
Fork 0
mirror of https://github.com/docker/docs.git synced 2026-11-01 22:34:29 +03:00
Code Activity

Moved info

Browse Source
This commit is contained in:
paigehargrave
2019-03-27 08:52:05 -04:00
committed by GitHub
parent 66ec66fdbc
commit 71db2daded
1 changed files with 0 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
ee/ucp/interlock/deploy/configure.md
View File

@@ -1,64 +0,0 @@
---
title: Configure the layer 7 routing service
description: Learn how to configure the layer 7 routing solution for UCP, that allows
you to route traffic to swarm services.
keywords: routing, proxy
---
[When enabling the layer 7 routing solution](index.md) from the UCP web UI,
you can configure the ports for incoming traffic. If you want to further
customize the layer 7 routing solution, you can do it by updating the
`ucp-interlock` service with a new Docker configuration.
Here's how it works:
1. Find out what configuration is currently being used for the `ucp-interlock`
service and save it to a file:
{% raw %}
```bash
CURRENT_CONFIG_NAME=$(docker service inspect --format '{{ (index .Spec.TaskTemplate.ContainerSpec.Configs 0).ConfigName }}' ucp-interlock)
docker config inspect --format '{{ printf "%s" .Spec.Data }}' $CURRENT_CONFIG_NAME > config.toml
```
{% endraw %}
2. Make the necessary changes to the `config.toml` file.
[Learn about the configuration options available](configuration-reference.md).
3. Create a new Docker configuration object from the file you've edited:
```bash
NEW_CONFIG_NAME="com.docker.ucp.interlock.conf-$(( $(cut -d '-' -f 2 <<< "$CURRENT_CONFIG_NAME") + 1 ))"
docker config create $NEW_CONFIG_NAME config.toml
```
3. Update the `ucp-interlock` service to start using the new configuration:
```bash
docker service update \
--config-rm $CURRENT_CONFIG_NAME \
--config-add source=$NEW_CONFIG_NAME,target=/config.toml \
ucp-interlock
```
By default the `ucp-interlock` service is configured to pause if you provide an
invalid configuration. The service won't restart without a manual intervention.
If you want the service to automatically rollback to a previous stable
configuration, you can update it with:
```bash
docker service update \
--update-failure-action rollback \
ucp-interlock
```
Another thing to be aware is that every time you enable the layer 7 routing
solution from the UCP UI, the `ucp-interlock` service is started using the
default configuration.
If you've customized the configuration used by the `ucp-interlock` service,
you'll have to update it again to use the Docker configuration object
you've created.