Oh! Thank you so much!
Sorry for the silly questions

On Thu, 7 Dec 2023, 14:41 Nick Couchman, <[email protected]> wrote:

> On Thu, Dec 7, 2023 at 2:15 AM Remush <[email protected]> wrote:
>
>> Oh okay, where does it get it ?
>>
>> Also after I removed the postgresql-42.6.0.jar I get a different error
>> message:
>>
>> ln: failed to create symbolic link 
>> '/home/guacamole/.guacamole/extensions/guacamole-auth-jdbc-postgresql-1.5.3.jar':
>>  File exists
>>
>>
> You should also remove this extension file from the directory/volume if
> you have manually added it. Again, the Docker startup script is meant to
> manage all of this for you. If you look in the startup script, in the
> PostgreSQL section:
>
>
> https://github.com/apache/guacamole-client/blob/212955c16c393c08f434f1def0ac12be36b09b2e/guacamole-docker/bin/start.sh#L296-L427
>
> You'll see these two lines toward the end:
>
>     # Add required .jar files to GUACAMOLE_LIB and GUACAMOLE_EXT
>     ln -s /opt/guacamole/postgresql/postgresql-*.jar "$GUACAMOLE_LIB"
>     ln -s /opt/guacamole/postgresql/guacamole-auth-*.jar "$GUACAMOLE_EXT"
>
> The Docker container already has the PostgreSQL JDBC driver and the
> Guacamole extension, and it links them when you configure Postgres. There
> is no need to place files manually in any directory, unless you're trying
> to enable an extension that isn't explicitly supported by the Docker
> script. However, Postgres is, so there's no need to do any manual file
> drops, etc.
>
> Perhaps do you also know why is there a .guacamole directory?
>> Because I set /etc/guacamole/ as the home directory
>>
>>
>>
> This is also determined by the startup script:
>
>
> https://github.com/apache/guacamole-client/blob/212955c16c393c08f434f1def0ac12be36b09b2e/guacamole-docker/bin/start.sh#L33-L36
>
> This allows the Tomcat service in the container to run as a non-root user
> without having to worry about the permissions of /etc/guacamole. There's no
> reason to try to change this, and the script will just override it, anyway.
>
> -Nick
>
>>

Reply via email to