Teslamate running in Docker on FWG

Follow

Nilanga

• February 23, 2022 21:27
• Edited

Does anyone here Teslamate running in Docker on Firewalla Gold?

I am not sure how to compose the docker-compose.yaml to incude IP address in the docker network subnet? Any ideas?

 

version: "3"

services:
  teslamate:
    image: teslamate/teslamate:latest
    restart: always
    environment:
      - ENCRYPTION_KEY= #insert a secure key to encrypt your Tesla API tokens
      - DATABASE_USER=teslamate
      - DATABASE_PASS= #insert your secure database password!
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
      - MQTT_HOST=mosquitto
    ports:
      - 4000:4000
    volumes:
      - ./import:/opt/app/import
    cap_drop:
      - all

  database:
    image: postgres:13
    restart: always
    environment:
      - POSTGRES_USER=teslamate
      - POSTGRES_PASSWORD= #insert your secure database password!
      - POSTGRES_DB=teslamate
    volumes:
      - teslamate-db:/var/lib/postgresql/data

  grafana:
    image: teslamate/grafana:latest
    restart: always
    environment:
      - DATABASE_USER=teslamate
      - DATABASE_PASS= #insert your secure database password!
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
    ports:
      - 3000:3000
    volumes:
      - teslamate-grafana-data:/var/lib/grafana

  mosquitto:
    image: eclipse-mosquitto:2
    restart: always
    command: mosquitto -c /mosquitto-no-auth.conf
    # ports:
    #   - 1883:1883
    volumes:
      - mosquitto-conf:/mosquitto/config
      - mosquitto-data:/mosquitto/data

volumes:
  teslamate-db:
  teslamate-grafana-data:
  mosquitto-conf:
  mosquitto-data:

0

• 

  sundar

  • March 09, 2023 03:33

  Are you able to run teslamate successfully? I am able to start teslamte on a different network but couldn't access any of the ports from the host. Ex: http//fiire.walla:4000. I am not sure how to fix it. I tried to run these directly on FWG instead of the subnet, but Postgres fails.  Does anyone succeed with teslamate setup on FWG?  

  0

  Comment actions Permalink
• 

  Nilanga

  • March 09, 2023 04:07

  Are you able to cut and paste your docker-compose.yaml. I think I am running into the same issue.

  0

  Comment actions Permalink
• 

  sundar

  • March 09, 2023 21:41

  I am using the default one from the site and did the below two commands to get egress and ingress traffic to these containers so that I can reach via browser with port.

  sudo ip route add 172.24.0.0/24 dev br-$(sudo docker network inspect teslamate_default |jq -r '.[0].Id[0:12]') table wan_routable

  sudo ip route add 172.24.0.0/24 dev br-$(sudo docker network inspect teslamate_default |jq -r '.[0].Id[0:12]') table lan_routable

  **Replace your network IPs where teslamate is running. 

   

   

   

  0

  Comment actions Permalink
• 

  sk0rp10

  • March 10, 2023 16:02

  Hi Sundar, I am trying to do the same and was wondering if it'd work running the teslamate and related containers in network host mode? This seems to work for homeBridge (see https://help.firewalla.com/hc/en-us/articles/360053184374-Guide-Install-HomeBridge-on-Firewalla-) 

  I am a bit nervous with adding manual routing entries to firewalla ... 

  0

  Comment actions Permalink
• 

  sundar

  • March 10, 2023 17:21

  I am running in bridge mode, not able do start the containers in the host network for some reason. 

  

  0

  Comment actions Permalink
• 

  sk0rp10

  • March 10, 2023 17:41

  Interesting. In my case they start in host mode but they don’t seem to open any ports in that case (no ports listed if I do docker ps in network host mode )

  0

  Comment actions Permalink
• 

  sundar

  • March 10, 2023 17:49

  My 'docker ps -a' does show all ports. Btw, I am also running portainer to make my docker operation easy.  We have some documentation on how to set this up as well. See if you can make it easier for you.

  0

  Comment actions Permalink
• 

  sk0rp10

  • March 16, 2023 18:15

  Okay so I utilised the same routing rules that you suggest in this article and that worked fine: I could connect to my Teslamate instance just fine.

  Now, the problem is that I would like to make the instance only accessible via VPN or LAN, and not via WAN as it currently is.

  Do you also see that your instance is accessible via WAN?

  I have a Wireguard VPN setup on the Gold and would like that only devices either on LAN or connected to that VPN can access the hosted Teslamate server on the Gold.

  Would you be able to help and suggest alternative route commands that can achieve that?

  Note: I have asked @firewalla and they suggested I’d better ask here ;)

  0

  Comment actions Permalink

Please sign in to leave a comment.