The script does likely need to be updated for some of the recent improvements to the Docker image, but I think you may be building in-progress, unreleased changes from the "main" branch in git.
There should be no issues with the images in Docker Hub, nor with the released source (such as the 1.5.5 tag or the source tarballs in the release archives). Are you seeing this with the released source/image? - Mike On June 28, 2024 9:21:35 PM PDT, Nathaniel Belles <mon99keymon99...@gmail.com> wrote: >Hi all, > >I'm reaching out because I believe I might have found an oversight in the >recent upgrades that were made to the docker build process that need some >updating. I was trying to deploy a new instance of guacamole in docker but I >found that I wasn't able to generate a PostgreSQL database. I was running the >`docker run --rm guacamole/guacamole /opt/guacamole/bin/initdb.sh --postgresql >> initdb.sql` command to build the initial database script but it failed >saying `cat: '/opt/guacamole/postgresql/schema/*.sql': No such file or >directory`. I inspected the deployment and found that the >`/opt/guacamole/postresql/` directory no longer exists in the current docker >implementation. I believe the schema for the databases has been moved to >`/opt/guacamole/extensions/guacamole-auth-jdbc/postgresql/schema` (and similar >for the other database frameworks) but was never updated in the >`/opt/guacamole/bin/initdb.sh` script. > >Am I correct that the `/opt/guacamole/bin/initdb.sh` script needs to be >updated to reflect the new schema locations for generating the database? > >Thanks. > >-Nathaniel Belles >
