cpcontainer/freetakserver repository overview

⁠FreeTAKServer on Cradlepoint Routers

Run FreeTAKServer⁠ as a container on Cradlepoint NCOS routers. TAK clients on the LAN connect directly to the router — no external server needed.

⁠Deploy to Cradlepoint

1. In NCM, edit the router configuration and go to System > Containers > Projects
2. Add a new project and give it a name
3. Paste the compose below into the compose tab
4. Save the project

version: "3"
services:
  freetakserver:
    image: cpcontainer/freetakserver
    container_name: freetakserver
    restart: unless-stopped
    user: "1000:1000"
    working_dir: /opt/fts
    security_opt:
      - no-new-privileges:true
    tmpfs:
      - /tmp:size=64M
      - /var/log:size=16M,uid=1000,gid=1000
    volumes:
      - fts_data:/opt/fts
    ports:
      - "8087:8087"   # CoT (ATAK clients connect here)
      - "8089:8089"   # SSL CoT
      - "8080:8080"   # HTTP TAK API
      - "8443:8443"   # HTTPS TAK API
      - "19023:19023" # REST API
      - "9000:9000"   # Federation
    environment:
      - FTS_COT_PORT=8087
      - FTS_SSLCOT_PORT=8089
      - FTS_DP_ADDRESS=0.0.0.0
      - FTS_USER_ADDRESS=0.0.0.0
      - FTS_API_ADDRESS=0.0.0.0
      - FTS_API_PORT=19023
      - FTS_FED_PORT=9000
volumes:
  fts_data:
    driver: local

⁠Connect ATAK

Add a server connection in ATAK:

• Address: the router's LAN IP
• Port: 8087
• Protocol: TCP
• No authentication required

⁠Configuration

FTS ports can be changed via environment variables in docker-compose.yml:

⁠Persistent Data

The /opt/fts volume stores the database, certificates, and configuration. Data survives container restarts and image updates.

⁠Troubleshooting

• Container won't start: Check container status in NCM or via status/container API for error messages.
• Clients can't connect: Verify the router firewall allows traffic on port 8087 from the LAN zone.
• Config changes not taking effect: FTS reads config at startup. Restart the container after changes.