You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pulled down latest code and completed the build process as per the instructions and was able to run docker-compose up -d correctly. No flags for IIQ_DB_TYPE, IIQ_PATCH used, defaulted to mysql for DB.
Upon running I noticed errors in the iiq-init container
/entrypoint.sh: line 36: sqlcmd: command not found
Looks like path to tools folder was incorrect, ran the following to correct sqlcmd error. ln -s /opt/mssql-tools18/bin/* /usr/local/bin/
Now receiving the following errors: 2023-10-26 15:37:58 Sqlcmd: Error: Microsoft ODBC Driver 18 for SQL Server : SSL Provider: [error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:self signed certificate]. 2023-10-26 15:37:58 Sqlcmd: Error: Microsoft ODBC Driver 18 for SQL Server : Client unable to establish connection. For solutions related to encryption errors, see https://go.microsoft.com/fwlink/?linkid=2226722.
The text was updated successfully, but these errors were encountered:
Pulled down latest code and completed the build process as per the instructions and was able to run docker-compose up -d correctly. No flags for IIQ_DB_TYPE, IIQ_PATCH used, defaulted to mysql for DB.
Upon running I noticed errors in the iiq-init container
/entrypoint.sh: line 36: sqlcmd: command not found
Looks like path to tools folder was incorrect, ran the following to correct sqlcmd error.
ln -s /opt/mssql-tools18/bin/* /usr/local/bin/
Now receiving the following errors:
2023-10-26 15:37:58 Sqlcmd: Error: Microsoft ODBC Driver 18 for SQL Server : SSL Provider: [error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:self signed certificate].
2023-10-26 15:37:58 Sqlcmd: Error: Microsoft ODBC Driver 18 for SQL Server : Client unable to establish connection. For solutions related to encryption errors, see https://go.microsoft.com/fwlink/?linkid=2226722.
The text was updated successfully, but these errors were encountered: