HI
After successfully running thingsboard in cluster using 'env=basic', i switched to 'env=monolith' and got the following error:

services.tb-monolith.ports value ['8080', '7070', '1883', '7070', '5683:5683/udp', '5685:5685/udp'] has non-unique elements

How do I go about fixing this?

Hi

Currently the docker-compose files present in this repository tend to favor a "full-on" approach.
Using the DATABASE variable in the main .env file, the user can either takes the postgres OR the cassandra road.

Often, it is convenient to take the best of both worlds by storing the entities in postgres and the telemetries in cassandra as described in the official documentation as the "hybrid" storage:

DATABASE_TS_TYPE=cassandra
DATABASE_ENTITIES_TYPE=sql

Do you intend to evolve this repository so it can handle this common scenario? Thanks.

Like written down in the Title:
The Version 3.4.2PE of the Docker Image of TB_Integration-Executor is not available at Docker Hub.

Workaround:
Change/Hardcode the Version (3.4.0PE) in docker-compose.yml

See title.

Specifically, I would like to fully understand what the following variables mean, and what their allowed values are:

• TB_SERVICE_ID (tb-pe-node) - does this need to be unique per container instance? The advanced option seems to indicate it does, but I could not find documentation on this.
• TB_SERVICE_TYPE (tb-pe-node) - I've seen various possible values, like tb-core, tb-rule-engine and monolith, but are there others?
• EDGES_ENABLED (tb-pe-node) - What does this enable/disable?

What are the defaults for these? Are there any more relevant environment vars?

It would be great if I could take a peek at the process that builds the PE container images; is this possible?

I have deployed Thingsboard PE using this docker-compose config. I'm trying to troubleshoot a transport error with MQTT and SSL, and I'd like to check the haproxy logs. I was expecting them at /var/log/haproxy.log (which points to a host volume) but can't find them. I also tried attaching to the container to view the live logs but there's no output. With this docker-compose configuration, are the haproxy logs generated and available? If not by default, would it be possible to adjust the configuration to output the logs to a volume outside the container? I can see the logs are published on 127.0.0.1 on the container, and should be picked up by syslog but not sure where they go from there.

with v3.2.0, running the install results in this error:

ERROR: manifest for store/thingsboard/tb-pe-node:latest not found: manifest unknown: manifest unknown

the way around it is to change in .env
TB_VERSION=latest
to
TB_VERSION=3.2.0PE

regards

What will be minimum system requirement for thingsboard pe docker with default setting in this repo?
we have aws m6a.xlarge which has 16GB ram with 4 vCpu and it shows 83% ram usage without much load
is it normal normal usage ?

Port 7070 is listed twice for tb-monolith inside monolith/docker-compose.yml, causing an error when running docker-install-tb.sh.