sebastienros/yessql

Running dev database no longer working with Docker after upgrading from OrchardCore 1.4 to 1.6

Closed this issue · 1 comments

I have reported this issue in OrchardCore. However, digging into the OrchardCore code base has led me here as the issue might actually be related to YesSql (possibly) Here is my ticket in the OrchardCore GitHub.

OrchardCMS/OrchardCore#14017

Essentially, if I try and run a setup of an OrchardCore CMS using OC version 1.5, everything works like it has done for ages. However, when I try the same using 1.6, my SQLServer database is only partially created. It creates the dbo.Document table fine and the dbo.Identifiers table fine. But does not create anymore tables.

1.5 looks like this after setup:
Orchard1-5-SQLServer

1.6 looks like this after setup:
Orchard1-6-SQLServer

1.6 also shows a 404 in a browser when trying to access the OrchardCore /Admin application. Nothing in the OC logs.
I am running this through docker with my database hosted on localhost in azure data studio. This setup has worked fine for a number of years with all sorts of Orchard configurations. Any ideas/thoughts would be greatly appreciated.

Further points to consider. I actually think this is likely an Apple M1 issue, relating to my Docker instance.
I have replicated on another M1 computer.
However, an intel computer works fine. Therefore, I will close this bug and dig into my docker instance instead.