L.H.
L.H.
So, I ran into this issue even after the fix. I was creating a new influx container and wiping the data volume mounted at /var/lib/influxdb2, but not the config volume...
> Yah, I had the same issue. > > From memory, I fixed this with something similar to this: > > ``` > git rm esp8266/libraries/LittleFS/lib/littlefs > git submodule add...
My first attempt was to upload the config to git. I used a setup container that downloads it and puts it into a shared volume. The telegraf container mounts this...
okay a personal fix, but nothing that changes the fundamental problem: ``` version: '3.9' services: telegraf: image: telegraf container_name: influxdb-telegraf depends_on: setup: condition: service_completed_successfully entrypoint: ["/bin/bash", "-c", "/etc/telegraf/wait-for-id-then-start-with-config.sh"] environment: DOCKER_INFLUXDB_INIT_MODE:...
Note the same issue on Stackoverflow https://stackoverflow.com/questions/62282117/best-way-to-reload-telegraf-configuration-when-running-in-a-container
> opc.tcp://user:[[email protected]](mailto:[email protected]):4840 this should be in the readme
> WHERE does my exported file actually end up? I cannot find it anywhere. Directly to the base of your internal storage it seems
Amazing! I just had this issue and now im patiently waiting for the release!
Gleiches für viele weitere Städte.
open sudo nano /etc/apt/sources.list.d/3v1n0-ubuntu-libfprint-vfs0090-jammy.list change jammy to focal worked for me