JoelJ / docker-compose-guacamole

Apache License 2.0
40 stars 15 forks source link

FATAL: Missing GUACD_HOSTNAME or "guacd" link #3

Open andreas-wolf opened 7 years ago

andreas-wolf commented 7 years ago

If I start with docker-compose up -d I can't connect. Log from guac_1 shows: FATAL: Missing GUACD_HOSTNAME or "guacd" link.

andreas-wolf commented 7 years ago

I added GUACD_HOSTNAME: guacd GUACD_PORT: 4822 to guac:environment:. Now I get: postgres_1 | ERROR: relation "guacamole_user" does not exist at character 322

allistera commented 7 years ago

"guacamole_user" does not exist at character is because the database dump in init/initdb.sql is out of date. I updated it by:

$ rm init/initdb.sql
$ docker-compose up -d
$ docker run --rm dockercomposeguacamole_guac_1 /opt/guacamole/bin/initdb.sh --postgres > init/initdb.sql

Then stop and delete all running containers from above and re-run docker-compose.

jomagam commented 7 years ago

@allistera You mean docker exec dockercomposeguacamole_guac_1 /opt/guacamole/bin/initdb.sh --postgres > init/initdb.sql Correct ?

cameronbraid commented 7 years ago

that worked for me

Starli0n commented 6 years ago

I followed the procedure but it does not work for me :-(

I still have the error:

postgres_1  | 2018-11-14 14:27:21.624 UTC [64] ERROR:  relation "guacamole_user" does not exist at character 322
postgres_1  | 2018-11-14 14:27:21.624 UTC [64] STATEMENT:  SELECT
postgres_1  |               user_id,
postgres_1  |               username,
postgres_1  |               password_hash,
postgres_1  |               password_salt,
postgres_1  |               password_date,
postgres_1  |               disabled,
postgres_1  |               expired,
postgres_1  |               access_window_start,
postgres_1  |               access_window_end,
postgres_1  |               valid_from,
postgres_1  |               valid_until,
postgres_1  |               timezone
postgres_1  |           FROM guacamole_user
postgres_1  |           WHERE
postgres_1  |               username = $1

Did I missed something ?

Starli0n commented 6 years ago

On my side, it was a permission issue and so /docker-entrypoint-initdb.d was skipped in the first place

I had a umask initially set to 077 and I set it to 0022 like the one defined inside the postgres image

This solved my issue

umask 0022

So the init folder and initdb.sql were set with the right permissions before starting the container

I tested with the last tags: