Skip to content

README.md

Latest commit

 

History

History
82 lines (64 loc) · 1.71 KB

README.md

File metadata and controls

82 lines (64 loc) · 1.71 KB

Docker Twingate Headless

This is for Twingate connect local network, using docker container!

Docker Compose (Port Forwarding)

You can use port forwarding to connect container local resources without using host network to connect (and set custom DNS).

version: "3"

services:
  twingate_client:
    container_name: twingate_client
    image: ghcr.io/docker-collection/twingate_headless:latest
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun
    environment:
      - 'SERVICE_KEY=One-Line-JSON-String'
      - 'ENABLE_PORT_FORWARDING=true'
      - 'PORT_MAPPINGS=80:example.local:8080,3306:example-mysql.local:3306'

Docker Compose (Host)

You can use network_mode: host, to make whole host connect twingate network. (Only need to specify Twingate DNS)

(Every time start container, internal IP address is different, so make sure you use the DNS)

DNS:

  • 100.95.0.251
  • 100.95.0.252
  • 100.95.0.253
  • 100.95.0.254
version: "3"

services:
  twingate_client:
    container_name: twingate_client
    image: ghcr.io/docker-collection/twingate_headless:latest
    network_mode: "host"
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun
    environment:
      - 'SERVICE_KEY=One-Line-JSON-String'
      - 'ENABLE_PORT_FORWARDING=false'

Example for custom dns

version: "3"

services:
  test:
    container_name: alpine-test
    image: alpine
    dns:
      - 100.95.0.251
      - 100.95.0.252
      - 100.95.0.253
      - 100.95.0.254
      - 1.1.1.1
      - 1.0.0.1
    command:
      - sleep
      - infinity

Reference