- Home
- Operations Guide
- Deploy applications with Swarm
- Interlock
- Deploy
- Offline installation considerations
Offline installation considerations#
To install Interlock on your cluster without an Internet connection, you must have the required Docker images loaded on your computer. This topic describes how to export the required images from a local instance of MCR and then load them to your Swarm-orchestrated cluster.
To export Docker images from a local instance:
-
Using a local instance of MCR, save the required 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.tarThis saves the following three files:
-
interlock.tar- the core Interlock application. -
interlock-extension-nginx.tar- the Interlock extension for NGINX. -
interlock-proxy-nginx.tar- the official NGINX image based on Alpine.
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. -
-
Copy the three files you just saved to each node in the cluster and load each image:
docker load < interlock.tar docker load < interlock-extension-nginx.tar docker load < interlock-proxy-nginx.tar
Refer to Deploy a layer 7 routing solution to continue the installation.
See also