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
dotnet new epi-alloy-mvc --name alloy-docker --output ./alloy-docker --enable-docker
You get an error that /opt/mssql-tools/bin/sqlcmd does not exists. This is because the newest version of mssql/server:2019 has its tools located at: /opt/mssql-tools18/bin/sqlcmd
It is still an open issue in github on mssql-docker, should the create-db.sh script be adjusted as a result of this change?
The text was updated successfully, but these errors were encountered:
In SQL Server 2022 (16.x) CU 14 and later versions, container images include the new mssql-tools18 package. The previous directory /opt/mssql-tools/bin is being phased out. The new directory for Microsoft ODBC 18 tools is /opt/mssql-tools18/bin, aligning with the latest tools offering. For more information about changes and security enhancements, see ODBC Driver 18.0 for SQL Server Released.
When initializing from a template using:
dotnet new epi-alloy-mvc --name alloy-docker --output ./alloy-docker --enable-docker
You get an error that
/opt/mssql-tools/bin/sqlcmd
does not exists. This is because the newest version ofmssql/server:2019
has its tools located at:/opt/mssql-tools18/bin/sqlcmd
It is still an open issue in github on mssql-docker, should the
create-db.sh
script be adjusted as a result of this change?The text was updated successfully, but these errors were encountered: