I am attempting to test ProGet v24 on a local docker stack currently hosting ProGet v23. However, ProGet fails to start due to a failure to initialize/upgrade the database. Note that I am using the mcr.microsoft.com/mssql/server:2022-latest
SQL Server and proget.inedo.com/productimages/inedo/proget:24
ProGet images in my Docker Compose file.
I also tested a similar scenario using a fresh database instance rather than upgrading an instance with existing ProGet v23 data. Unfortunately, I am seeing the same errors.
The specific failure logs that I am seeing when testing with a fresh (empty) database are shown below. The final error message repeats indefinitely as ProGet attempts to start but fails.
ProGet version is 24.0.11.10.
Current DB schema version is unknown.
Database is not initialized; initializing...
Database initialized.
Executing untracked script DDL-DML/0000. Untracked/00. EnsureDbo.sql...
Executing untracked script DDL-DML/0000. Untracked/10. Block 5.3 Upgrades.sql...
Executing untracked script DDL-DML/0000. Untracked/10. Block SQL Server 2005.sql...
Executing tracked script DDL-DML/v1-6/v1/0002. 0.1.0/10 SET DATABASE PROPERTIES.sql...
Error number: 226
Line number: 1
ALTER DATABASE statement not allowed within multi-statement transaction.
Error number: 226
Line number: 1
ALTER DATABASE statement not allowed within multi-statement transaction.
DDL-DML/v1-6/v1/0002. 0.1.0/10 SET DATABASE PROPERTIES.sql executed successfully.
Executing tracked script DDL-DML/v1-6/v1/0002. 0.1.0/20 CREATE TYPES.sql...
Incorrect syntax near 'GO'.
'CREATE RULE' must be the first statement in a query batch.
Incorrect syntax near 'GO'.
Incorrect syntax near 'GO'.
ProGet version is 24.0.11.10.
Current DB schema version is unknown.
Scripts not executed; at least one script has unresolved errors.
Use the "errors" command to view unresolved errors, or use the --force argument to run anyway.
Any help with this would be greatly appreciated.