Additional container information

This space is place Holder and will be revised.

Manually Adding the Container to an Existing System

When adding iQs to a larger container deployment, the best practice is to utilize the existing tools that are administering the system. This document assumes the reader has experience using containers, and only covers the unique variables needed to make an iQs run.

Network Considerations

Livewire+ AES67 defaults to using multicast traffic. In order for a container to be able to subscribe to audio streams, it must have a MAC address assigned to it and have direct access to the AoIP network. The two network types provided in Docker Engine that meet the requirements are macvlan and host. More information about these network types can be found here.

Deploying iQs

iQs can be deployed using any solution that can control Docker containers. This document contains examples of Docker Compose. Example 1 shows how to use multiple iQs instances on a single host, while Example 2 demonstrates how to use a single instance. Both examples will require some variables to be adjusted before using them.

Example 1: Multiple instances

version: '2.4'
services:
  iqs:
    restart: unless-stopped
    image: quay.io/telosalliance/iqs  
    hostname: iQs:"your_host_name"
    networks:
      telosmacvlan:
           ipv4_address: ${IPV4_ADDRESS}
    volumes:
      - ./config:/config
    cap_add:
      - SYS_NICE
networks:
  telosmacvlan:
    external:
      name: telosmacvlan

Example 2: Single instance

version: '2.4' 
services: 
   iqs: 
       restart: unless-stopped 
       image: quay.io/telosalliance/iqs  
       hostname: "your_host_name" 
       network_mode: host 
       volumes:
         - ./config:/config
       cap_add:
         - SYS_NICE