philhawthorne/docker-influxdb-grafana

A Docker container which runs InfluxDB and Grafana ready for persisting data

docker-influxdb-grafana's Issues

port settings

hi Phil,
thanks for your pages, finally im almost getting there....

following your setup guide I've managed to run influxdb and grafana like this:

docker run -d \
  --name docker-influxdb-grafana \
  -p 3003:3003 \
  -p 3004:8083 \
  -p 8086:8086 \
  -p 22022:22 \
  -v /volume1/docker/InfluxDB:/var/lib/influxdb \
  -v /volume1/docker/Grafana:/var/lib/grafana \
  --restart=always \
  philhawthorne/docker-influxdb-grafana:latest

since i am running HomeAssistant on a Pi3 and not locally on the Synology, i cant use localhost, but have it pointed to my nas on .

In HomeAssistant configuration.yaml I've added

influxdb:
host: ipaddress
port: 3004

but then error log shows:

2018-01-25 15:15:34 ERROR (MainThread) [homeassistant.setup] Error during setup of component influxdb
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/requests/models.py", line 371, in prepare_url
    scheme, auth, host, port, path, query, fragment = parse_url(url)
  File "/usr/lib/python3.6/site-packages/urllib3/util/url.py", line 199, in parse_url
    raise LocationParseError(url)
urllib3.exceptions.LocationParseError: Failed to parse: ipaddress:3004:8086

It seems the default port 8086 is added after whichever host is written?

What port should i change best for the influxdb to start running correctly? Leaving the port 3004 out doesn't work either, it won't see Influxdb at all then

2018-01-25 16:54:09 ERROR (SyncWorker_12) [homeassistant.components.influxdb] Database host is not accessible due to '', please check your entries in the configuration file (host, port, etc.) and verify that the database exists and is READ/WRITE.

btw, since inluxdb and grafana are running on my password protected NAS, do we need to enter those credentials in the setup/config too? 'Homeassistant' being a user on the Synology and changing rights to read/write on the docker would not suffice?

Hope you can have a quick look,
thanks!
Marius

Store influx database on USB-Stick?

Is it possible to store the db on a usb stick ?

how to edit grafana.ini?thx.

how to edit grafana.ini?thx.

how is the influxdb database kept?

Hi Phil,

I would have rather sent an email, but couldn't find one anywhere. Not on your homepage, not on your gh profile, ...

I'm wondering how the database is not deleted when destroying the container. I was playing around with the official influxdb image which I have deployed via kubernetes. However, every time I delete the pod, the db gets wiped out.
Is it just a matter of setting -v /path/for/grafana:/var/lib/grafana or did you do something special in your image?

Unfortunately we have a requirement to separate grafana and influxdb in separate environments, thus I cannot use your image. But it is a great approach and I would use it in a heartbeat, if I was allowed to...

Port for armv7 (Raspberry Pi)

Could you port this good docker image to armv7 (Raspberry Pi)? Or could you explain me how I could do it?

Grafana crashing near start

$ docker run --name docker-influxdb-grafana -p 3003:3003 -p 3004:8888 -p 8086:8086 -v ~/Documents/influxdb:/var/lib/influxdb -v ~/Documents/grafana:/var/lib/grafana philhawthorne/docker-influxdb-grafana:latest
/usr/lib/python2.7/dist-packages/supervisor/options.py:298: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2019-08-15 15:43:32,521 CRIT Supervisor running as root (no user in config file)
2019-08-15 15:43:32,521 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2019-08-15 15:43:32,531 INFO RPC interface 'supervisor' initialized
2019-08-15 15:43:32,531 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-08-15 15:43:32,532 INFO supervisord started with pid 1
2019-08-15 15:43:33,535 INFO spawned: 'chronograf' with pid 9
2019-08-15 15:43:33,538 INFO spawned: 'influxdb' with pid 10
2019-08-15 15:43:33,541 INFO spawned: 'grafana' with pid 11
2019-08-15 15:43:34,591 INFO success: chronograf entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-15 15:43:34,591 INFO success: influxdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-15 15:43:34,591 INFO success: grafana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-15 15:43:39,593 INFO exited: influxdb (exit status 0; expected)
2019-08-15 15:43:45,638 INFO exited: grafana (exit status 1; not expected)
2019-08-15 15:43:46,641 INFO spawned: 'grafana' with pid 126
2019-08-15 15:43:46,663 INFO exited: grafana (exit status 0; not expected)
2019-08-15 15:43:47,667 INFO spawned: 'grafana' with pid 132
2019-08-15 15:43:47,683 INFO exited: grafana (exit status 0; not expected)
2019-08-15 15:43:49,688 INFO spawned: 'grafana' with pid 138
2019-08-15 15:43:49,706 INFO exited: grafana (exit status 0; not expected)
2019-08-15 15:43:52,711 INFO spawned: 'grafana' with pid 145
2019-08-15 15:43:52,727 INFO exited: grafana (exit status 0; not expected)
2019-08-15 15:43:53,729 INFO gave up: grafana entered FATAL state, too many start retries too quickly

This is with a clean docker env (no other images or containers downloaded or running). The mapped volumes appear to be populated correctly after start.

$ grep eror /var/log/grafana/grafana.log 
t=2019-08-15T15:52:40+0000 lvl=eror msg="Server shutdown" logger=server reason="System signal: terminated"

(re)Starting grafana from supervisorctl results in the same behavior.

upgrade?

Hi Phil nice docker image, just wondering if you were planning to update it to the latest grafana/influxdb???

Typo in docker Hub Documentation

Hi Phil,

great fan, love your blog posts. Just a minor issue I stumbled upon when coming from https://hub.docker.com/r/philhawthorne/docker-influxdb-grafana/ I had a hard time getting the docker up and running. It seems there is a typo in the documentation on docker hub: instead of -p 3004:8888 \ it should be -p 3004:8083 \ like in the Readme here on github.

Cheers, really appreciate your work and looking forward to your next automation post! :)

Influxdb won't start.

Hi Phil

I've been using this for sometime now with no problems at all. I did a reboot on my system today and all my dockers came back fine, including this one, but for some reason influxdb hasn't started, Grafana has. Is there anything I can do to kick start it please?

Cheers
Mark

How to edit grafana.ini

How can I edit the grafana.ini file to enable anonymous? I have tried adding /var/lib/grafana/grafana.ini and copied over the grafana.ini file from your repo, and then enabled auth.anonymous and bounced the container, but nothing has changed.

Is my path correct? Am I missing something else? I am pretty new to working with Docker images.

Problem starting the container on Raspberry Pi

Hi,

I'm poking docker and Influx/Grafana first time on Raspberry Pi. Followed the README, but container wont start:

pi@raspi4:~ $ docker start docker-influxdb-grafana
docker-influxdb-grafana
pi@raspi4:~ $ docker ps -a
CONTAINER ID        IMAGE                                          COMMAND             CREATED             STATUS                     PORTS               NAMES
6ce36eebef10        philhawthorne/docker-influxdb-grafana:latest   "/run.sh"           11 minutes ago      Exited (1) 2 seconds ago                       docker-influxdb-grafana

Trying with interactive:

pi@raspi4:~ $ docker start -i docker-influxdb-grafana
standard_init_linux.go:211: exec user process caused "exec format error"

Did I miss something, or should it even work on Raspberry Pi?

Update?

Hello

Do you plan any version update? I cannot run some plugin because the grafana version is too old. I did not check if influxdb needs also update

thanks

Processes exiting

I haven't touched this container in a while, but I'd like to get back to it. I checked on it recently and it looks like all 3 processes are failing.

What can I look at? This is running on a synology

/usr/lib/python2.7/dist-packages/supervisor/options.py:298: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2019-10-18 14:29:22,096 CRIT Supervisor running as root (no user in config file)
2019-10-18 14:29:22,097 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2019-10-18 14:29:22,197 INFO RPC interface 'supervisor' initialized
2019-10-18 14:29:22,197 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-10-18 14:29:22,197 INFO supervisord started with pid 1
2019-10-18 14:29:23,200 INFO spawned: 'chronograf' with pid 10
2019-10-18 14:29:23,202 INFO spawned: 'influxdb' with pid 11
2019-10-18 14:29:23,205 INFO spawned: 'grafana' with pid 12
2019-10-18 14:29:24,675 INFO success: chronograf entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-18 14:29:24,676 INFO success: influxdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-18 14:29:24,676 INFO success: grafana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-18 14:29:25,685 INFO exited: influxdb (exit status 1; not expected)
2019-10-18 14:29:26,689 INFO spawned: 'influxdb' with pid 83
2019-10-18 14:29:27,759 INFO success: influxdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-18 14:29:28,629 INFO reaped unknown pid 92
2019-10-18 14:29:32,783 INFO exited: influxdb (exit status 0; expected)
2019-10-18 14:29:36,244 INFO exited: grafana (exit status 1; not expected)
2019-10-18 14:29:37,247 INFO spawned: 'grafana' with pid 146
2019-10-18 14:29:37,291 INFO exited: grafana (exit status 0; not expected)
2019-10-18 14:29:38,294 INFO spawned: 'grafana' with pid 152
2019-10-18 14:29:38,326 INFO exited: grafana (exit status 0; not expected)
2019-10-18 14:29:40,330 INFO spawned: 'grafana' with pid 158
2019-10-18 14:29:40,356 INFO exited: grafana (exit status 0; not expected)
2019-10-18 14:29:43,361 INFO spawned: 'grafana' with pid 164
2019-10-18 14:29:43,383 INFO exited: grafana (exit status 0; not expected)
2019-10-18 14:29:44,385 INFO gave up: grafana entered FATAL state, too many start retries too quickly

InfluxDB Failing to load on start

Here is what I see:

I can get into Grafana, but influxdb is failing.

root@653cddbb36d5:/var/log/grafana# tail -f /var/log/grafana/grafana.log
t=2019-08-20T21:28:12+0000 lvl=info msg="Initializing ServerLockService" logger=server
t=2019-08-20T21:28:12+0000 lvl=info msg="Initializing TracingService" logger=server
t=2019-08-20T21:28:12+0000 lvl=info msg="Initializing UsageStatsService" logger=server
t=2019-08-20T21:28:12+0000 lvl=info msg="Initializing UserAuthTokenService" logger=server
t=2019-08-20T21:28:12+0000 lvl=info msg="Initializing CleanUpService" logger=server
t=2019-08-20T21:28:12+0000 lvl=info msg="Initializing NotificationService" logger=server
t=2019-08-20T21:28:12+0000 lvl=info msg="Initializing provisioningServiceImpl" logger=server
t=2019-08-20T21:28:12+0000 lvl=info msg="Initializing Stream Manager"
t=2019-08-20T21:28:12+0000 lvl=info msg="HTTP Server Listen" logger=http.server address=0.0.0.0:3003 protocol=http subUrl= socket=
t=2019-08-20T21:31:30+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=root method=GET path=/api/datasources/proxy/1/query status=502 remote_addr=192.168.1.52 time_ms=0 size=0 referer="http://192.168.1.52:3003/?orgId=1"

Originally posted by @moore66982 in #24 (comment)

Security issue

Hi, why does the image permit root login with password? I’ve just noticed that after two attacks. It’s not needed by docker.

No "direct" option for InfluxDB connection in Grafana

I create using:

docker run -d --name docker-influxdb-grafana -p 192.168.2.4:3003:3003 -p 192.168.2.4:8083:8083 -p 192.168.2.4:8086:8086 -v /home/homeassistant/influxdb:/var/lib/influxdb -v /home/homeassistant/grafana:/var/lib/grafana philhawthorne/docker-influxdb-grafana:edge

(I changed port 3004, surely makes no difference)

In Grafana's Add Source for InfluxDB, there are choices of "Server" and "Browser" no "Direct" as per docs. Neither option works, both produce an error on "Save and Test"

InfluxDB (chronograf) not reachable

When I install this docker on my Synology NAS. exactly as listed. I can see the Grafana webpage, but I don't see the influxDB webpage. My grafana is running on 192.168.0.30:3003, but if I go to 192.168.0.30:3004 it says the site is not reachable. How can I check what is happening? and what could be a potential reason for this?

InfluxDB not written to disk

I started the container and wrote a bunch of data to it. After killing the container and restarting it all the data was gone. Any idea why?

Heres my dockerfile:

version: '3'
services:
  mongo:
    ports:
      - "27017:27017"
    volumes:
      - .dockerdata/mongodb:/data/db
    environment:
      - MONGO_INITDB_ROOT_USERNAME=
      - MONGO_INITDB_ROOT_PASSWORD=
    image: mongo
  grafana-influx:
    ports:
      - "3003:3003"
#      - "3004:8083"
      - "8086:8086"
    volumes:
      - .dockerdata/influxdb:/var/lib/influxdb
      - .dockerdata/grafana:/var/lib/grafana
    image: philhawthorne/docker-influxdb-grafana:latest

Persist changes in grafana and influxdb

Hi, silly question.
But how do I persist my changes to Grafana and InfluxDB.
Every time I restart everything is lost...

Thanks in advance

security vulnerability in Grafana

https://grafana.com/blog/2020/06/03/grafana-6.7.4-and-7.0.2-released-with-important-security-fix/

probably should not have this (grafana) exposed to open internet, but if you are...

likely need to bump grafana version to at 6.7.4+

Incorrect access control vulnerability (CVE-2020-13379)

We received a security report to [email protected] on May 14, 2020, about a vulnerability in Grafana regarding the avatar feature. It was later identified as affecting Grafana versions from 3.0.1 to 7.0.1. CVE-2020-13379 has been assigned to this vulnerability.

The avatar feature in Grafana 3.0.1 through 7.0.1 has an SSRF Incorrect Access Control issue that allows remote code execution. This vulnerability allows any unauthenticated user/client to make Grafana send HTTP requests to any URL and return its result to the user/client. This can be used to gain information about the network that Grafana is running on.

If for some reason you cannot upgrade, the impact can be mitigated by blocking access to the avatar feature by blocking the /avatar/* URL via a web application firewall, load balancer, reverse proxy, or similar. It can also be mitigated by restricting access to Grafana.

No ports binding

Hello!

maybe stupid question.
When I launch the latest container, I see no exposed ports.

In the readme I see (and really neeed) at least 3

Where I'm wrong?

Thanks

Imported data shows wrong timestamp

Hi,

iam currently trying to import old values from home-assistant but the timestamp is not working correctly.

This Timestamp 1588221453 should be 2020-04-30 06:37:33.004826
The date is correct in Influx but the time 6:12.

I have imported via API to use seconds as precision but its the same whith nanosecond converted timestamps.
Adding entrys without timestamps gives the current correct time.

Any Ideas?

Grafana not loading

Have setup the docker following the instructions. I created 2 shares on /volume1 of my Synology in the same way. Both with the same permissions.
/volume1/InfluxDB is being written to, /volume1/Grafana isnt.
Even when i change it to /volume1/InfluxDB/grafana, influx is writing data, Grafana isnt.

t=2017-12-06T14:50:32+0000 lvl=info msg="Starting Grafana" logger=main version=4.1.1 commit=v4.1.1 compiled=2017-01-12T08:48:03+0000
t=2017-12-06T14:50:32+0000 lvl=info msg="Config loaded from" logger=settings file=/usr/share/grafana/conf/defaults.ini
t=2017-12-06T14:50:32+0000 lvl=info msg="Config loaded from" logger=settings file=/etc/grafana/grafana.ini
t=2017-12-06T14:50:32+0000 lvl=info msg="Config overriden from command line" logger=settings arg="default.paths.data=/var/lib/grafana"
t=2017-12-06T14:50:32+0000 lvl=info msg="Config overriden from command line" logger=settings arg="default.paths.logs=/var/log/grafana"
t=2017-12-06T14:50:32+0000 lvl=info msg="Config overriden from command line" logger=settings arg="default.paths.plugins=/var/lib/grafana/plugins"
t=2017-12-06T14:50:32+0000 lvl=info msg="Config overriden from Environment variable" logger=settings var="GF_DATABASE_TYPE=sqlite3"
t=2017-12-06T14:50:32+0000 lvl=info msg="Path Home" logger=settings path=/usr/share/grafana
t=2017-12-06T14:50:32+0000 lvl=info msg="Path Data" logger=settings path=/var/lib/grafana
t=2017-12-06T14:50:32+0000 lvl=info msg="Path Logs" logger=settings path=/var/log/grafana
t=2017-12-06T14:50:32+0000 lvl=info msg="Path Plugins" logger=settings path=/var/lib/grafana/plugins
t=2017-12-06T14:50:32+0000 lvl=info msg="Initializing DB" logger=sqlstore dbtype=sqlite3
t=2017-12-06T14:50:32+0000 lvl=info msg="Starting DB migration" logger=migrator
t=2017-12-06T14:50:32+0000 lvl=eror msg="Fail to initialize orm engine" logger=sqlstore error="Sqlstore::Migration failed err: unable to open database file\n"

Startup issue

Hi Phil,

I'm trying to get started with influxdb and having trouble getting this container to start up. Using the quick start command:

docker run -d \
  --name docker-influxdb-grafana \
  -p 3003:3003 \
  -p 3004:8083 \
  -p 8086:8086 \
  -v /path/for/influxdb:/var/lib/influxdb \
  -v /path/for/grafana:/var/lib/grafana \
  philhawthorne/docker-influxdb-grafana:latest

(except changing the paths for my system)

I get the following output from docker logs. Any ideas?

/usr/lib/python2.7/dist-packages/supervisor/options.py:298: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2020-04-08 00:24:47,220 CRIT Supervisor running as root (no user in config file)
2020-04-08 00:24:47,221 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2020-04-08 00:24:47,233 INFO RPC interface 'supervisor' initialized
2020-04-08 00:24:47,233 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2020-04-08 00:24:47,233 INFO supervisord started with pid 1
2020-04-08 00:24:48,239 INFO spawned: 'chronograf' with pid 10
2020-04-08 00:24:48,245 INFO spawned: 'influxdb' with pid 11
2020-04-08 00:24:48,248 INFO spawned: 'grafana' with pid 12
2020-04-08 00:24:49,315 INFO success: chronograf entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-04-08 00:24:49,315 INFO success: influxdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-04-08 00:24:49,315 INFO success: grafana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-04-08 00:24:49,326 INFO exited: influxdb (exit status 1; not expected)
2020-04-08 00:24:49,359 INFO spawned: 'influxdb' with pid 74
2020-04-08 00:24:50,382 INFO success: influxdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-04-08 00:24:50,462 INFO reaped unknown pid 83
2020-04-08 00:24:55,393 INFO exited: influxdb (exit status 0; expected)
2020-04-08 00:25:00,398 INFO exited: grafana (exit status 1; not expected)
2020-04-08 00:25:01,402 INFO spawned: 'grafana' with pid 147
2020-04-08 00:25:01,420 INFO exited: grafana (exit status 0; not expected)
2020-04-08 00:25:02,430 INFO spawned: 'grafana' with pid 153
2020-04-08 00:25:02,447 INFO exited: grafana (exit status 0; not expected)
2020-04-08 00:25:04,458 INFO spawned: 'grafana' with pid 159
2020-04-08 00:25:04,476 INFO exited: grafana (exit status 0; not expected)
2020-04-08 00:25:07,484 INFO spawned: 'grafana' with pid 165
2020-04-08 00:25:07,501 INFO exited: grafana (exit status 0; not expected)
2020-04-08 00:25:08,508 INFO gave up: grafana entered FATAL state, too many start retries too quickly

Easy way to install plugins? .env

Is there a way to install plugins? What is the preferred method docker exce -it container /bin/bash
grafana-cli install xxx?
Or could you do a .env file something like this?
GRAFANA_PLUGINS=grafana-piechart-panel
https://github.com/alekece/tig-stack/blob/master/.env

Grafana doesn't load in iFrames

@philhawthorne thanks have been rebuilding my docker containers for the last day and have found several issues I didn't had before. One of the, is while I'm trying to have grafana loaded embed with HA in a iframe, noticed I need to change the grafana.ini to allow that. Didn't managed to do ssh to the localhost as it was giving me several errors, managed to achieve that searching for the file using the command find . -name "grafana.ini" and then just edit via vi command, it worked for em :)

root@pauloserver:/volume2/@docker/aufs/diff/3ef8f4769cc95373371b06b595946674dde27939eb9500d9c9e8cef363e6f1a8/etc/grafana# vi grafana.ini

Originally posted by @paazevedo in #7 (comment)

Deploying docker-influxdb-grafana on fargate

Hello,

Have you ventured looking at deploying this image on AWS Fargate? Would it be possible ot leverage EFS filesystem for persistance?

Shekar

Update Grafana to latest version (7.2)

Can you update to Grafana 7.2? You can tag it with a new version if needed.

Chronograf config resetting over and over

Hey hey,

Awesome container, thank you so much. Got it up and running np, feeding data in, I can access everything, it's great.

Every time I go to my Chronograf tab though, it's on the "Welcome to Chronograf" screen again and wanting me to set it up. I'm assuming the container has restarted since I last looked at the tab (I'll pay more attention next time) and that perhaps some persistence is missing? Here's my swarm conf -

version: "3.3"

services:
  AIO:
    image: philhawthorne/docker-influxdb-grafana:latest
    volumes:
     - type: volume
       source: influxdb
       target: /var/lib/influxdb
       volume:
         nocopy: true
     - type: volume
       source: grafana
       target: /var/lib/grafana
       volume:
         nocopy: true
     - type: volume
       source: influxdb-conf
       target: /etc/influxdb
       volume:
         nocopy: true
    networks:
      - swarmnet
    environment:
      - TZ=America/New_York
    ports:
      - 3003:3003
      - 3004:8083
      - 8086:8086
      - 8089:8089/udp
    deploy:
      placement:
        constraints:
          - node.platform.arch==x86_64
      labels:
        - "traefik.enable=true"
        - "traefik.docker.network=swarmnet"
        - "traefik.chronograf.port=8083"
        - "traefik.chronograf.frontend.rule=Host:chronograf.cntr"
        - "traefik.grafana.port=3003"
        - "traefik.grafana.frontend.rule=Host:grafana.cntr"

networks:
  swarmnet:
    external:
      name: swarmnet

volumes:
  influxdb:
    driver_opts:
      type: "nfs"
      o: "addr=192.168.0.55,nolock,soft,rw"
      device: ":/volume1/container_volumes/influxdb-grafana/influxdb"
  grafana:
    driver_opts:
      type: "nfs"
      o: "addr=192.168.0.55,nolock,soft,rw"
      device: ":/volume1/container_volumes/influxdb-grafana/grafana"
  influxdb-conf:
    driver_opts:
      type: "nfs"
      o: "addr=192.168.0.55,nolock,soft,rw"
      device: ":/volume1/container_volumes/influxdb-grafana/influxdb-conf"

Chronograph UI not working

Hi,

I am all new to this, I have followed your tutorials and all went well so far apart from this. I am not able to run this docker. Here is an extract from the log file from NAS:

2019-10-05 04:42:23,602 INFO gave up: grafana entered FATAL state, too many start retries too quickly
2019-10-05 04:42:22,601 INFO exited: grafana (exit status 0; not expected)
2019-10-05 04:42:22,578 INFO spawned: 'grafana' with pid 166
2019-10-05 04:42:19,573 INFO exited: grafana (exit status 0; not expected)
2019-10-05 04:42:19,550 INFO spawned: 'grafana' with pid 159
2019-10-05 04:42:17,546 INFO exited: grafana (exit status 0; not expected)
2019-10-05 04:42:17,523 INFO spawned: 'grafana' with pid 153
2019-10-05 04:42:16,520 INFO exited: grafana (exit status 0; not expected)
2019-10-05 04:42:16,496 INFO spawned: 'grafana' with pid 147
2019-10-05 04:42:15,493 INFO exited: grafana (exit status 1; not expected)
2019-10-05 04:42:11,586 INFO exited: influxdb (exit status 0; expected)
2019-10-05 04:42:07,265 INFO reaped unknown pid 89
2019-10-05 04:42:06,584 INFO success: influxdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-05 04:42:05,488 INFO spawned: 'influxdb' with pid 80
2019-10-05 04:42:04,521 INFO exited: influxdb (exit status 1; not expected)
2019-10-05 04:42:04,510 INFO success: grafana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-05 04:42:04,509 INFO success: influxdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-05 04:42:04,508 INFO success: chronograf entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-10-05 04:42:03,157 INFO spawned: 'grafana' with pid 15
2019-10-05 04:42:03,154 INFO spawned: 'influxdb' with pid 14
2019-10-05 04:42:03,152 INFO spawned: 'chronograf' with pid 13
2019-10-05 04:42:02,150 INFO supervisord started with pid 1
2019-10-05 04:42:02,149 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2019-10-05 04:42:02,149 INFO RPC interface 'supervisor' initialized
2019-10-05 04:42:02,119 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2019-10-05 04:42:02,118 CRIT Supervisor running as root (no user in config file)
  'Supervisord is running as root and it is searching '
/usr/lib/python2.7/dist-packages/supervisor/options.py:298: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.```

InfluxDB enviroment variables

Does this image allows creation of influxdb by using enviroment variables like described here?

version: "3.3"
 services:
  influxdb-grafana:
    image: philhawthorne/docker-influxdb-grafana:latest
    container_name: "influxdb-grafana"
    environment:
      - INFLUXDB_DB=${INFLUXDB_DB}
      - INFLUXDB_ADMIN_USER=${INFLUXDB_ADMIN_USER}
      - INFLUXDB_ADMIN_PASSWORD=${INFLUXDB_ADMIN_PASSWORD}
      - INFLUXDB_USER=${INFLUXDB_USER}
      - INFLUXDB_USER_PASSWORD=${INFLUXDB_USER_PASSWORD}
    restart: always
    ports:
      - 3003:3003
      - 3004:8083
      - 8086:8086
    volumes:
      - influxdb:/var/lib/influxdb
      - grafana:/var/lib/grafana

Here is part of my docker-compose file. From what I can see those variables are ignored.

cookie_samesite breaks setCookie

cookie_samesite=none in grafana.ini breaks login, Set-Cookie header blocked since it lacks secure attribute.

I changed it to be commented out in /etc/grafana/grafana.ini inside the docker container (so it defaults to Lax), and that solved the issue.

InfluxDB Error: database not found: InfluxDB

I log in to localhost:3003, but whenever I try to add a new database default entry (according to the instructions), I get this error:

InfluxDB Error: database not found: InfluxDB

Can you please help?

The requested image's platform (linux/amd64) does not match

I have successfully build the project on my AMD laptop running ubuntu 20.04.

But on 'bionic' arm [linux/arm64/v8] i'm getting the following issue.

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
c98ee4ad1cc273e93672a0bd810c2cd9b28834cdc61f26e22dad63f5636c5239

I have tried to debug the dockerfile it's intelligent to pick automatic arm or amd on the go.
I am new to docker please help me out how can i successfully install the setup on my ARM.

docker --version

Docker version 20.10.5, build 55c4c88

lscpu

Architecture:         aarch64
Byte Order:           Little Endian
CPU(s):               6
On-line CPU(s) list:  0-3
Off-line CPU(s) list: 4,5
Thread(s) per core:   1
Core(s) per socket:   2
Socket(s):            2
Vendor ID:            Nvidia
Model:                0
Model name:           ARMv8 Processor rev 0 (v8l)
Stepping:             0x0
CPU max MHz:          1907.2000
CPU min MHz:          115.2000
BogoMIPS:             62.50
L1d cache:            64K
L1i cache:            128K
L2 cache:             2048K
L3 cache:             4096K
Flags:                fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp

Thanks