Komponist relies on Docker Compose V2 (written in golang) as opposed to the Docker Compose V1 (which was written in python).
Since Compose v1 is bound to be Deprecated in June 2023, the current way to use
docker composeis throughansible.builtin.shellmodule as opposed to through thecommunity.docker.docker_composemodule which relies on python module.
There is some traction on community.docker collection to integrate Docker Compose V2. If it gets
integrated the possible ansible.builtin.shell module might be replaced with the respective module in the
future.
Komponist will resolve the relative paths e.g., ./ to absolute path on the machine where Komponist is executed.
This implies that the docker-compose.yml deployed on a remote machine must also have the same paths to the configuration
file as that on the controller node (where Komponist is executed).
This caveat may be mitigated if one uses a well-known directories like /usr/share/ or /etc/ because these paths are
reflected similarly on the Controller as well as Remote machines
Since QuestDB / InfluxDBv2's UI does not provide any configuration to render the UI behind a root path, it is not possible to render
the UI under /influxdbv2 or /questdb path. At the moment, it is only possible to view the UI when visiting the following links:
http://influxdbv2.localhost
OR
http://questdb.localhost
There is a caveat when it comes to uploading the tarballs offline, where the uri Ansible Module
is unable upload the tarball in a correct manner as the Node-RED API throws BAD_GZIP errors. This
maybe because of an inherent logic of uri module dependent on some pre-encoding the tarball with
Base64 which the Node-RED Admin API is unable to decode and hence cannot extract further on.
This problem is mitigated by using command module to perform the bootstrapping via curl within
bootstrap_nodered.yml playbook