mirror of https://github.com/docker/docs.git
Remove Interlock manual deployment pages
This commit is contained in:
Joao Fernandes
Jim Galasyn
parent
b2f0a31d77
commit
53e3709c55
Binary file not shown.
|
Before Width: | Height: | Size: 31 KiB |
|
|
@ -1,88 +0,0 @@
|
|||
---
|
||||
title: Deploy Interlock manually
|
||||
description: Learn about Interlock, an application routing and load balancing system
|
||||
for Docker Swarm.
|
||||
keywords: ucp, interlock, load balancing
|
||||
ui_tabs:
|
||||
- version: ucp-3.0
|
||||
orhigher: false
|
||||
---
|
||||
|
||||
{% if include.version=="ucp-3.0" %}
|
||||
|
||||
## Requirements
|
||||
|
||||
- [Docker](https://www.docker.com) version 17.06+ is required to use Interlock
|
||||
- Docker must be running in [Swarm mode](https://docs.docker.com/engine/swarm/)
|
||||
- Internet access (see [Offline Installation](offline.md) for installing without internet access)
|
||||
|
||||
## Deployment
|
||||
Interlock uses a configuration file for the core service. The following is an example config
|
||||
to get started. In order to utilize the deployment and recovery features in Swarm we will
|
||||
create a Docker Config object:
|
||||
|
||||
```bash
|
||||
$> cat << EOF | docker config create service.interlock.conf -
|
||||
ListenAddr = ":8080"
|
||||
DockerURL = "unix:///var/run/docker.sock"
|
||||
PollInterval = "3s"
|
||||
|
||||
[Extensions]
|
||||
[Extensions.default]
|
||||
Image = "interlockpreview/interlock-extension-nginx:2.0.0-preview"
|
||||
Args = ["-D"]
|
||||
ProxyImage = "nginx:alpine"
|
||||
ProxyArgs = []
|
||||
ProxyConfigPath = "/etc/nginx/nginx.conf"
|
||||
ServiceCluster = ""
|
||||
PublishMode = "ingress"
|
||||
PublishedPort = 80
|
||||
TargetPort = 80
|
||||
PublishedSSLPort = 443
|
||||
TargetSSLPort = 443
|
||||
[Extensions.default.Config]
|
||||
User = "nginx"
|
||||
PidPath = "/var/run/proxy.pid"
|
||||
WorkerProcesses = 1
|
||||
RlimitNoFile = 65535
|
||||
MaxConnections = 2048
|
||||
EOF
|
||||
oqkvv1asncf6p2axhx41vylgt
|
||||
```
|
||||
|
||||
Next we will create a dedicated network for Interlock and the extensions:
|
||||
|
||||
```bash
|
||||
$> docker network create -d overlay interlock
|
||||
```
|
||||
|
||||
Now we can create the Interlock service. Note the requirement to constrain to a manager. The
|
||||
Interlock core service must have access to a Swarm manager, however the extension and proxy services
|
||||
are recommended to run on workers. See the [Production](production.md) section for more information
|
||||
on setting up for an production environment.
|
||||
|
||||
```bash
|
||||
$> docker service create \
|
||||
--name interlock \
|
||||
--mount src=/var/run/docker.sock,dst=/var/run/docker.sock,type=bind \
|
||||
--network interlock \
|
||||
--constraint node.role==manager \
|
||||
--config src=service.interlock.conf,target=/config.toml \
|
||||
interlockpreview/interlock:2.0.0-preview -D run -c /config.toml
|
||||
sjpgq7h621exno6svdnsvpv9z
|
||||
```
|
||||
|
||||
There should be three (3) services created. One for the Interlock service,
|
||||
one for the extension service and one for the proxy service:
|
||||
|
||||
```bash
|
||||
$> docker service ls
|
||||
ID NAME MODE REPLICAS IMAGE PORTS
|
||||
lheajcskcbby modest_raman replicated 1/1 nginx:alpine *:80->80/tcp *:443->443/tcp
|
||||
oxjvqc6gxf91 keen_clarke replicated 1/1 interlockpreview/interlock-extension-nginx:2.0.0-preview
|
||||
sjpgq7h621ex interlock replicated 1/1 interlockpreview/interlock:2.0.0-preview
|
||||
```
|
||||
|
||||
The Interlock traffic layer is now deployed. Continue with the [Deploying Applications](/usage/index.md) to publish applications.
|
||||
|
||||
{% endif %}
|
||||
|
|
@ -1,45 +0,0 @@
|
|||
---
|
||||
title: Deploy Interlock offline
|
||||
description: Learn about Interlock, an application routing and load balancing system
|
||||
for Docker Swarm.
|
||||
keywords: ucp, interlock, load balancing
|
||||
ui_tabs:
|
||||
- version: ucp-3.0
|
||||
orhigher: false
|
||||
---
|
||||
|
||||
{% if include.version=="ucp-3.0" %}
|
||||
|
||||
To install Interlock on a Docker cluster without internet access the Docker images will
|
||||
need to be loaded. This guide will show how to export the images from a local Docker
|
||||
engine to then be loaded to the Docker Swarm cluster.
|
||||
|
||||
First, using an existing Docker engine save the images:
|
||||
|
||||
```bash
|
||||
$> docker save docker/interlock:latest > interlock.tar
|
||||
$> docker save docker/interlock-extension-nginx:latest > interlock-extension-nginx.tar
|
||||
$> docker save nginx:alpine > nginx.tar
|
||||
```
|
||||
|
||||
Note: replace `docker/interlock-extension-nginx:latest` and `nginx:alpine` with the corresponding
|
||||
extension and proxy image if you are not using Nginx.
|
||||
|
||||
You should have two files:
|
||||
|
||||
- `interlock.tar`: This is the core Interlock application
|
||||
- `interlock-extension-nginx.tar`: This is the Interlock extension for Nginx
|
||||
- `nginx:alpine`: This is the official Nginx image based on Alpine
|
||||
|
||||
Copy these files to each node in the Docker Swarm cluster and run the following to load each image:
|
||||
|
||||
```bash
|
||||
$> docker load < interlock.tar
|
||||
$> docker load < interlock-extension-nginx.tar
|
||||
$> docker load < nginx:alpine.tar
|
||||
```
|
||||
|
||||
After running on each node, you can continue to the [Deployment](index.md#deployment) section to
|
||||
continue the installation.
|
||||
|
||||
{% endif %}
|
||||
Loading…
Reference in New Issue