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.
Set up the IS Gateway service on a server with Internet access, then add a docker engine.
Before you begin
Watch this 4-minute video to learn how to set up a local container registry.
What you should know
- Install IS Gateway on a server with Internet access.
- Set up the IS Gateway service to use the Genetec™ production token.
- Add a docker engine.
- Add the driver containers you need.
Run Command Prompt as administrator.
- In the Windows taskbar, click and enter cmd.
- In the search result, right-click Command Prompt and click Run as administrator.
In the Command Prompt window, enter the following command:
docker psThe available driver containers are listed.
Copy the name of the container image you need from the
Move to a folder where you want to generate an archive of this container image.
Use the following command:
where <MyArchiveFolder> is the path to your folder.
Generate an archive of the container image with the following command:
Following our previous example, the command would be:
docker save --output <ArchiveName>.tar <ImageName>:<Image TAG>
docker save --output magos-v1.02.tar geneteccispidsregistryproduction.azurecr.io/magos:1.02
- Copy the archived container image you generated to the server that has no Internet access.
- On that server, run Command Prompt as administrator.
- Move to the folder where you copied the archived container image.
Load the container image with the following command:
docker load -–input <ArchiveName>.tar
Ensure that the image has been correctly loaded with the following command:
docker psThis container image can now be used by the IS Gateway service using the local registry option.
- Repeat the same process with all the driver container images you need.