[ 
https://issues.apache.org/jira/browse/GUACAMOLE-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881688#comment-17881688
 ] 

Nick Couchman commented on GUACAMOLE-1978:
------------------------------------------

[~frankthetank]:
I've been testing out a couple of things related to the errors you've reported, 
here, and I've found a couple of things that you might try to see if it 
resolves the issues you're seeing:
* First of all, please make sure that you have not, somehow, configured Docker 
to do container linking, which is considered legacy, and I'm seeing some 
problems related to that (extra variables get introduced that cause issues). 
See discussion on GUACAMOLE-374.
* Second, in your guacamole_test container, please change the "POSTGRESQL_USER" 
variable to "POSTGRESQL_USERNAME". This is not updated in the documentation, 
yet, since the updated documentation has not been released for 1.6.0, but the 
POSTGRESQL_USER variable won't work with 1.6.0 at the moment.
* Finally, I'm not sure why you are mapping the /opt/guacamole/extensions 
directory in the container through from your host, but there should not be any 
reason for that. Guacamole handles that internally, unless you've go some 
custom extension you're trying to map through. Below is my working docker 
compose file.

{code}
version: '3.9'
services:
  guacd:
    container_name: guacd
    image: guacamole/guacd:1.6.0
    networks:
      - guacnetwork_test
    restart: always
    volumes:
    - /docker/data/guacamole/drive:/drive:rw
    - /docker/data/guacamole/recordings:/recordings:rw
  postgres_guac:
    container_name: postgres_guac
    environment:
      PGDATA: /var/lib/postgresql/data/pgdata
      POSTGRES_DB: guacamole
      POSTGRES_PASSWORD: yummyGuacamole
      POSTGRES_USER: guacamole
    image: postgres:latest
    networks:
      - guacnetwork_test
    restart: always
    volumes:
    - 
/docker/build/guacamole/guacamole-client/extensions/guacamole-auth-jdbc/modules/guacamole-auth-jdbc-postgresql/schema:/docker-entrypoint-initdb.d:ro
    - /docker/data/guacamole/db:/var/lib/postgresql/data:rw
  guacamole:
    container_name: guacamole_test
    depends_on:
    - guacd
    - postgres_guac
    environment:
      GUACD_HOSTNAME: guacd
      POSTGRESQL_DATABASE: guacamole
      POSTGRESQL_HOSTNAME: postgres_guac
      POSTGRESQL_PASSWORD: yummyGuacamole
      POSTGRESQL_USERNAME: guacamole
      POSTGRESQL_AUTO_CREATE_ACCOUNTS: true
      LOG_LEVEL: debug
      TZ: America/New_York
    image: guacamole/guacamole:1.6.0
    networks:
      - guacnetwork_test
    volumes:
      - /docker/data/guacamole/recordings:/recordings:rw
    ports:
      - 8080:8080
    restart: always
networks:
  guacnetwork_test:
    driver: bridge
{code}

> Unable to login on build from main branch
> -----------------------------------------
>
>                 Key: GUACAMOLE-1978
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1978
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole
>    Affects Versions: 1.6.0
>            Reporter: Frank The Tank
>            Priority: Major
>             Fix For: 1.6.0
>
>
> When building the client from the main branch or the staging/1.6.0 on an 
> arm64 container, it builds just fine, but after launching the containers, I 
> am unable to login with the default guacadmin/guacadmin. Just says login 
> failed. The errors in the logs are:
> {code:java}
> 21:16:06.353 [http-nio-8080-exec-8] DEBUG 
> o.a.g.a.f.FileAuthenticationProvider - User mapping file 
> "/tmp/guacamole-home.Ydf78SGgoV/user-mapping.xml" does not exist and will not 
> be read.14321:16:06.354 [http-nio-8080-exec-8] WARN  
> o.a.g.event.EventLoggingListener - Authentication attempt from [<REDACTED>, 
> 10.10.10.2] for user "guacadmin" failed: unknown error (no specific failure 
> recorded)14421:16:06.355 [http-nio-8080-exec-8] DEBUG 
> o.a.g.rest.RESTExceptionMapper - Client request rejected: Permission Denied. 
> {code}
> I'm using an initialized Postgres DB for the backend, and have made sure the 
> psql extension and lib are available in the container. 
> I would try 1.5.5, but it fails to build on arm64 due to maven issues. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to