On Sun, Sep 1, 2024 at 10:15 PM Lauren Phillips <circ...@circenn.city.invalid> wrote:
> From what I can tell the environment variable POSTGRESQL_PORT is > completely ignored. Changing it to an arbitrary number still outputs the > same value of "postgresql-port: tcp://10.108.245.56:5432" in > /home/guacamole/.guacamole/guacamole.properties > 10.108.245.56 is the ip of the postgres service > It seems like in your environment something is re-writing the postgresql-port value in guacamole.properties to more of full URI for the PostgreSQL service. If I use docker to pull the image and specify a port with the POSTGRESQL_PORT environment variable, it gets written as expected: docker pull guacamole/guacamole:latest # docker run --name test-guac -e POSTGRESQL_HOSTNAME=database.example.com -e POSTGRESQL_PORT=6543 -e POSTGRESQL_DATABASE=guac -e POSTGRESQL_USER=guac -e POSTGRESQL_PASSWORD=guac -e GUACD_HOSTNAME=guacd.example.com -e GUACD_PORT=4822 -d -p 8080:8080 guacamole/guacamole # docker exec -it test-guac /bin/bash guacamole@92ba8fca8da0:/opt/guacamole$ cat /home/guacamole/.guacamole/guacamole.properties # guacamole.properties - generated Mon Sep 2 02:27:41 AM UTC 2024 guacd-hostname: guacd.example.com guacd-port: 4822 postgresql-username: guac postgresql-password: guac postgresql-database: guac postgresql-hostname: database.example.com postgresql-port: 6543 Is there something else in those transforms or YAML files that takes the various DB information and tries to rewrite it into a URI? -NIck >
