Closed ukkarikari closed 3 months ago
This is related to the InfluxDB config in the docker.env
file, i forgot to include some of the variables there. I fixed it with this commit: https://github.com/SIDN/entrada2/commit/4b8c4fd2280a2ed9d021bb99cc0f87518f6809cf
One thing, the name of the inflxudb bucket has changed to entrada2, but if you already have an existing influxdb docker volume, this new bucket will not be created automatically. You have to create it manually or just remove the old docker volume, then the bucket, using the correct name, is created again during startup.
delete volume command: docker volume rm docker_entradaInfluxDbVolume
We managed to install via Docker, but we would like to activate rdata recording, we edited the corresponding parameter in entrada2/src/main/resources/application.yml, but apparently the installation via Docker does not respect this configuration. How to enable rdata data writing when installing via docker? Thanks!
you can override any variable from application.yml using enviroment variables.
option entrada.rdata.enabled: true
can be expressed as an env var using ENTRADA_RDATA_ENABLED=true
closing as fixed, was as config issue
When running the application in docker, fails to deploy with the following error:
Couldn't trace the error back to a specific area of the source code. Replicated in three different machines running Debian 12 and Arch Linux kernel 6.9.7.