Build the FaceTec Server when Inbound Network Traffic is Blocked
Learn how to build the FaceTec Server when Inbound Network Traffic is Blocked.
Restricted Network Access
Some System Architectures restrict access to the Internet, preventing Developers & System Administrators from installing and running the FaceTec Server & Usage Log Server via FaceTec's default steps. When Internet Access is restricted, resources cannot be automatically pulled from the Internet using Docker.
Running the FaceTec Server via Docker
You will need to Build the FaceTec Server Docker Image on a machine outside of Your Restricted Network Access Environment and transfer it via a Removable Storage Device or a Secure Intranet Connection. If Docker is not already installed on the Server within Your Restricted Network Access Environment, then you will need to install the Docker Engine from its Static Binary.
Step 1: Build FaceTec Server Docker Image on an Outside Machine
- Download the FaceTec Server onto a machine with Docker and Internet Access (i.e. outside of the Environment with Blocked Inbound Network Traffic).
- Extract the FaceTec Server.
- In FaceTec-Server-Webservice/Docker-Deployment-Scripts, build the Docker Images by running the following command:
docker compose build facetec_server_webservice_prebuilt_with_usage_log_server facetec_usage_log_server - Create a tarball of the two Docker Images by running the following command:
- Usage Log Server:
docker save -o usage_log_server.tar facetec_usage_log_server:latest. - FaceTec Server Webservice:
docker save -o facetec_server_webservice.tar facetec_server_webservice_prebuilt_with_usage_log_server:latest.
- Usage Log Server:
- On success, the tarball will be created in the root directory of the FaceTec Server.
Step 2: Transfer Docker Image & Compose File to Your Environment with Blocked Inbound Network Traffic
Removable Storage Device:
- Copy the tarballs and docker-compose.yml file onto Your Removable Storage Device.
- Follow the process outlined by Your Company for transferring data via a Removable Storage Device to the Environment with Blocked Inbound Network Traffic.
- On success, the tarballs and docker-compose.yml will now be on Your Server with Restricted Network Access.
Intranet Connection:
- Copy the tarballs onto Your Server. For Linux, use the following command:
- Usage Log Server:
scp /Path/to/usage_log_server.tar <USERNAME>@<SERVER_ADDRESS>:/Path/on/server. - FaceTec Server Webservice:
scp /Path/to/facetec_server_webservicer.tar <USERNAME>@<SERVER_ADDRESS>:/Path/on/server.
- Copy the docker-compose.yml file onto Your Server. For Linux, use the following command:
scp /Path/to/docker-compose.yml <USERNAME>@<SERVER_ADDRESS>:/Path/on/server. - On success, the tarball and docker-compose.yml will now be on Your Server with Restricted Network Access.
Step 3: Build Docker from its Binaries (if Docker is not installed)
- Download the corresponding Static Binary as a tarball from Docker's Static Binaries.
- Transfer the Docker tarball in the same manner as Step 2: Transfer Docker Image & Compose File to Your Environment with Blocked Inbound Network Traffic.
- Extract Docker via the tar command:
tar xzvf /Path/to/Docker_Tarball. - Copy Docker into a directory that is a part of Your Executable Path. /usr/bin is recommended:
sudo cp docker/* /usr/bin. - Run the Docker Daemon:
sudo dockerd &.- Important Note: This step may first require iptables to be configured and running on the system.
- On success, you will get the Usage Definition for Docker when running
sudo docker.
Step 4: Install the Docker Compose CLI Plugin (if Docker Compose is not installed)
- Download the latest Docker Compose Plugin for your system's architecture on a machine with Internet Access.
Example:curl -SL https://github.com/docker/compose/releases/download/v2.20.0/docker-compose-linux-x86_64 -o docker-compose. - Transfer docker-compose in the same manner as Step 2: Transfer Docker Image & Compose File to Your Environment with Blocked Inbound Network Traffic.
- Create a directory to run the Docker Compose CLI Plugin with Root Priveleges.
Example on AWS EC2 Instance:sudo mkdir -p /usr/local/lib/docker/cli-plugins. - Move the Docker Compose CLI Plugin into the directory created in the previous step:
sudo mv docker-compose /usr/local/lib/docker/cli-plugins/docker-compose. - Add execute permissions to the Docker Compose CLI Plugin:
chmod +x /usr/local/lib/docker/cli-plugins/docker-compose. - On success, you will get the Usage Definition for Docker Compose when running
sudo docker compose.
Step 5: Load and Run FaceTec Server Docker Container
- On Your Server with Restricted Network Access, go to the directory with the FaceTec Server's Docker Image.
- Load the Docker Images into Docker:
- Usage Log Server:
sudo docker load -i usage_log_server.tar. - FaceTec Server Webservice:
sudo docker load -i facetec_server_webservice.tar.
- Usage Log Server:
- From the same directory as the docker-compose.yml file, run
sudo docker compose up facetec_server_webservice_prebuilt_with_usage_log_server facetec_usage_log_server. - On success, Docker will run the FaceTec Server and the FaceTec Server will initialize successfully.