Offline installation considerations

Estimated reading time: 1 minute

This topic applies to Docker Enterprise.

The Docker Enterprise platform business, including products, customers, and employees, has been acquired by Mirantis, inc., effective 13-November-2019. For more information on the acquisition and how it may affect you and your business, refer to the Docker Enterprise Customer FAQ.

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 docker/ucp-interlock:3.2.6 > interlock.tar
$> docker save docker/ucp-interlock-extension:3.2.6 > interlock-extension-nginx.tar
$> docker save docker/ucp-interlock-proxy:3.2.6 > interlock-proxy-nginx.tar


Replace docker/ucp-interlock-extension:3.2.6 and docker/ucp-interlock-proxy:3.2.6 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.

routing, proxy, interlock