netdata docker on FWGold

Pinned

Comments

7 comments

  • Avatar
    Scott G

    Never mind, got it working in host mode.  Once I claimed it on netdata.cloud all the other stats popped in.  Not sure if that did it or I just needed to be patient.

    0
    Comment actions Permalink
  • Avatar
    Jim S

    @scott, can you share the specific steps you used to get this up and running?  Thanks.

    0
    Comment actions Permalink
  • Avatar
    Sukumar Patel

    I tried it out and here it is

    /home/pi/.firewalla/run/docker/netdata/docker-compose.yaml

    version: '3.4'
    services:
    netdata:
    image: netdata/netdata
    container_name: netdata
    hostname: ThePatelsFWG
    ports:
    - 19999:19999
    restart: unless-stopped
    cap_add:
    - SYS_PTRACE
    security_opt:
    - apparmor:unconfined
    volumes:
    - ./netdataconfig/netdata:/etc/netdata:ro
    - netdatalib:/var/lib/netdata
    - netdatacache:/var/cache/netdata
    - /etc/passwd:/host/etc/passwd:ro
    - /etc/group:/host/etc/group:ro
    - /proc:/host/proc:ro
    - /sys:/host/sys:ro
    - /etc/os-release:/host/etc/os-release:ro
    network_mode: host
    volumes:
    netdatalib:
    netdatacache:

    The commands to try the docker image and add the token to the cloud instance (The command is fetched from the portal)

    sudo docker-compose up
    sudo docker exec -it netdata netdata-claim.sh -token=xxxx -rooms=yyyy -url=https://app.netdata.cloud

    Once verified that its working, persist it as below

    Stop the image by hitting ctrl+c

    Run the below command

    sudo docker-compose up --no-start
    sudo systemctl start docker-compose@netdata

    Verify that its working with 

    sudo systemctl status docker-compose@netdata
    sudo docker ps

    Persist it by creating the below file /home/pi/.firewalla/config/post_main.d/02StartNextData.sh

    sudo systemctl start docker
    sudo systemctl start docker-compose@netdata

     

    sudo systemctl start docker-compose@netdata

     

     

    0
    Comment actions Permalink
  • Avatar
    Scott G

    I generally followed the steps for setting up the Homebridge docker here: https://help.firewalla.com/hc/en-us/articles/360053184374-Guide-Install-HomeBridge-on-Firewalla-Gold-Beta-  but used "netdata" instead of "homebridge" for the directory names.  The section on setting up mdns isn't relevant, so I skipped that.

    Here's my docker-compose.yaml

    version: '3'
    services:
    netdata:
    image: netdata/netdata
    container_name: netdata
    hostname: fire.walla # set to fqdn of host
    network_mode: host
    ports:
    - 19999:19999
    restart: unless-stopped
    cap_add:
    - SYS_PTRACE
    security_opt:
    - apparmor:unconfined
    volumes:
    - netdataconfig:/etc/netdata
    - netdatalib:/var/lib/netdata
    - netdatacache:/var/cache/netdata
    - /etc/passwd:/host/etc/passwd:ro
    - /etc/group:/host/etc/group:ro
    - /proc:/host/proc:ro
    - /sys:/host/sys:ro
    - /etc/os-release:/host/etc/os-release:ro

    volumes:
    netdataconfig:
    netdatalib:
    netdatacache:
    0
    Comment actions Permalink
  • Avatar
    Scott G

    There's a further step to claim the node on netdata.cloud by copy and pasting in a docker exec command with a token from your netdata.cloud account. Mine looked like this:

    docker exec -it netdata netdata-claim.sh -token=<LONG TOKEN STRING GOES HERE> -rooms=<ROOM ID # GOES HERE> -url=https://app.netdata.cloud
    0
    Comment actions Permalink
  • Avatar
    Jim S

    @Scott this works great.  

    0
    Comment actions Permalink
  • Avatar
    Bjørn Arne Restad

    I just installed it on the metal as Linux Device

    Works great.

    More info at: https://app.netdata.cloud

    0
    Comment actions Permalink

Please sign in to leave a comment.