Setting up a local container registry - Inter-System Gateway 1.1

Inter-System Gateway Configuration Guide 1.1

Applies to
Inter-System Gateway 1.1
Last updated
Content type
Guides > Plugin and extension guides
Inter-System Gateway
Plugin and extension guides

By default, the IS Gateway service uses a container registry hosted on Azure. If your IS Gateway server does not have Internet access, you must set up the registry on a local drive.

Before you begin

Set up the IS Gateway service on a server with Internet access, then add a docker engine.

What you should know

Watch this 4-minute video to learn how to set up a local container registry.


  1. Install IS Gateway on a server with Internet access.
  2. Set up the IS Gateway service to use the Genetec™ production token.
  3. Add a docker engine.
  4. Add the driver containers you need.
  5. Run Command Prompt as administrator.
    1. In the Windows taskbar, click and enter cmd.
    2. In the search result, right-click Command Prompt and click Run as administrator.
  6. In the Command Prompt window, enter the following command:
    docker ps
    The available driver containers are listed.
    Command Prompt window showing the docker ps command and the list of available driver containers.
  7. Copy the name of the container image you need from the IMAGE column.
    For example,
  8. Move to a folder where you want to generate an archive of this container image.
    Use the following command:
    cd <MyArchiveFolder>
    where <MyArchiveFolder> is the path to your folder.
  9. Generate an archive of the container image with the following command:
    docker save --output <ArchiveName>.tar <ImageName>:<Image TAG>
    Following our previous example, the command would be:
    docker save --output magos-v1.02.tar
  10. Copy the archived container image you generated to the server that has no Internet access.
  11. On that server, run Command Prompt as administrator.
  12. Move to the folder where you copied the archived container image.
  13. Load the container image with the following command:
    docker load -–input <ArchiveName>.tar
  14. Ensure that the image has been correctly loaded with the following command:
    docker ps
    This container image can now be used by the IS Gateway service using the local registry option.
  15. Repeat the same process with all the driver container images you need.