jamie-mint

I'm getting errors with the host networking in the compose context. (because compose renames network hostnames) the below example is illustrative: ``` [mycodo_telegraf] 2022-07-19T00:19:47Z E! [outputs.influxdb] When writing to [http://localhost:8086]:...

Brilliant, yes I was just discovering this. Another piece of the equation is that my embedded docker framework/platform (balenaOS) doesn't accept a parent dir context (i.e. `context: ../`). Just converted...

I'm able to docker-compose successfully on `influx2` branch but I think there's a new issue on `master`, as `mycodo_flask` crashes now on initialization: ``` Traceback (most recent call last): File...

I would imagine this is because your volume is already initialized with some data (i.e. not a cold start)? Is there perhaps side-effects from running mycodo the normal way first?...

Yea these are from as sanitized an environment as I could conjur (at `0fc6105b142b35e5b39759fbee067d252921f1cd`) One of the things I saw in the logs from mycodo_flask `/bin/sh: 1: influxd: not found`