docs/ee/ucp/interlock/deploy/offline-install.md

title	description	keywords
Offline installation considerations	Learn how to to install Interlock on a Docker cluster without internet access.	routing, proxy, interlock

{% include enterprise_label_shortform.md %}

To install Interlock on a Docker cluster without internet access, the Docker images must be loaded. This topic describes how to export the images from a local Docker engine and then load them to the Docker Swarm cluster.

First, using an existing Docker engine, save the images:

$> docker save {{ page.ucp_org }}/ucp-interlock:{{ page.ucp_version }} > interlock.tar
$> docker save {{ page.ucp_org }}/ucp-interlock-extension:{{ page.ucp_version }} > interlock-extension-nginx.tar
$> docker save {{ page.ucp_org }}/ucp-interlock-proxy:{{ page.ucp_version }} > interlock-proxy-nginx.tar

Note

Replace {{ page.ucp_org }}/ucp-interlock-extension:{{ page.ucp_version }} and {{ page.ucp_org }}/ucp-interlock-proxy:{{ page.ucp_version }} with the corresponding extension and proxy image if you are not using Nginx.

You should have the following three files:

• interlock.tar: This is the core Interlock application.
• interlock-extension-nginx.tar: This is the Interlock extension for NGINX.
• interlock-proxy-nginx.tar: This is the official NGINX image based on Alpine.

Next, copy these files to each node in the Docker Swarm cluster and run the following commands to load each image:

$> docker load < interlock.tar
$> docker load < interlock-extension-nginx.tar
$> docker load < interlock-proxy-nginx.tar

Next steps

After running on each node, refer to the Deploy section to continue the installation.