Offline installation considerations

Offline installation considerations

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 MCR and then load them to the Docker Swarm cluster.

First, using an existing MCR, save the images:

$> docker save mirantis/ucp-interlock:3.3.11 > interlock.tar
$> docker save mirantis/ucp-interlock-extension:3.3.11 > interlock-extension-nginx.tar
$> docker save mirantis/ucp-interlock-proxy:3.3.11 > interlock-proxy-nginx.tar

Note

Replace mirantis/ucp-interlock-extension:3.3.11 and mirantis/ucp-interlock-proxy:3.3.11 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 Deploy a layer routing solution to continue the installation.