Docker compose installation in a VLAN

Installation
1

Hello,

I wanted to install the connector in its own VLAN using docker-compose, and I had some issues putting in the sysctl parameter. Maybe it’s a good idea to support docker-compose as an official installation platform as well?

Thanks

1 Like
2

Same request here. Docker Compose is (for many) the preferred and recommended deployment method, it would be good to have Docker Compose as an official deployment method.

@kalpik :did you manage to get it working? I’d be much interested in your experience.

1 Like
3

Haven’t had the time to play around with it yet. Will keep you posted :slight_smile:

4

Hi @kalpik and @anon2545132,

Twingate does support Docker Compose as a way to deploy Connectors, here is a sample one:

version: '3'
services:
  twingate_connector:
    container_name: twingate-connector
    restart: always
    image: 'twingate/connector:1'
    environment:
      - TENANT_URL=https://<tenant_slug>.twingate.com
      - ACCESS_TOKEN=<access_token>
      - REFRESH_TOKEN=<refresh_token>
    sysctls:
      net.ipv4.ping_group_range: "0 2147483647"

You will need to insert your tenant name, Connector refresh and access tokens but the rest should be standard. (PS: the net.ipv4.ping_group_name parameter is there to ensure the underlying image can handle ICMP / ping request so it isnt strictly required but you should add it if you intend to use ping for troubleshooting when connecting to remote resources).

1 Like
5

Thanks, but I think the indentation is not correct here. The container_name and everything below it should be indented one to the left. But I will try this out later. Just quite busy these days :slight_smile:

6

So, finally got a chance to play with this, and this works:

version: "3"
services:
  twingate:
    image: twingate/connector:1
    container_name: twingate
    environment:
      - TENANT_URL=<>
      - ACCESS_TOKEN=<>
      - REFRESH_TOKEN=<>
      - TWINGATE_LABEL_HOSTNAME=<>
    sysctls:
      net.ipv4.ping_group_range: "0 2147483647"
    restart: always
1 Like
7

Great! thanks @kalpik! I have submitted a request to add this to the official documentation.

1 Like
8

One thing I would add when adding to the documentation is if you’d prefer to pass env vars via env file or on the cli, replace <> with $TENANT_URL, $ACCESS_TOKEN etc

2 Likes
9

Thanks for the sample!
I keep getting the error:
“Error response from daemon: Get “https://registry-1.docker.io/v2/”: dial tcp 18.215.138.58:443: connect: no route to host”
Anyone any idea on how to solve this?

btw: the indentation in Bren’s post seems perfect to me

10

@anon2545132 it looks like the location you are running Docker Compose from may not be able to connect to the public Docker Registry for some reason. Is that the case? (It needs to pull the Connector image from the public Docker Registry)

11

It was wrong before, and was edited to fix it :slight_smile:

12

Yes, to my surprise (everything works fine) that seems to be the case. Thanks for your reply.

13

It is now part of the official documentation!

1 Like