Sql docker container exists everytime when running in the XP mode

[VipraB]

Solr is not able to connect to the SQL docker container .The Processing enginer when trying to connect to the SQL it is not able to make the connection and gives the below error.

docker logs --details 8ff951b4c3d3

Existing Sitecore databases found in 'C:\data\'...

Attaching 'sc_Core'...

Attaching 'sc_Exm.master'...

Attaching 'sc_Experienceforms'...

Attaching 'sc_MarketingAutomationAzure'...

Attaching 'sc_Marketingautomation'...

Attaching 'sc_Master'...

Attaching 'sc_Messaging'...

Attaching 'sc_Processing.Engine.Storage'...

Attaching 'sc_Processing.Engine.Tasks'...

Attaching 'sc_Processing.pools'...

Attaching 'sc_Processing.tasks'...

Attaching 'sc_Referencedata'...

Attaching 'sc_Reporting'...

Attaching 'sc_Sessions'...

Attaching 'sc_Web'...

Attaching 'sc_Xdb.Collection.Shard0'...

Attaching 'sc_Xdb.Collection.Shard1'...

Attaching 'sc_Xdb.Collection.ShardMapManager'...

Preparing Sitecore databases...

Invoke-Sqlcmd : Invalid object name
'Sitecore.Xdb.Collection.ShardMapManager.__ShardManagement.ShardsGlobal'.
At C:\Boot.ps1:44 char:1

• Invoke-Sqlcmd -Query ("UPDATE [Sitecore.Xdb.Collection.ShardMapManage ...

•   + CategoryInfo          : InvalidOperation: (:) [Invoke-Sqlcmd], SqlPowerS
   hellSqlExecutionException
    + FullyQualifiedErrorId : SqlError,Microsoft.SqlServer.Management.PowerShe
   ll.GetScriptCommand
  

[pbering]

Keyword here is "Existing Sitecore databases found in 'C:\data'..." ... you properly have run XM or another compose before so whenever you are switching you need to clean the .\data folder, you can use the .\Clean-Data.ps1 script for that. Else fresh databases / indexes for the given topology will not be seeded.

[VipraB]

Thanks that worked.

But I need to run solr and sitecore as on secure port by generating the ssl certificates.
Can you help me understand where we can do the required changes to achieve this.

[pbering]

Good :)

I can't point you to an example but what we are doing (sometime locally and always in upstream environments) is to put a proxy in front that does SSL termination.

Looks like this:

                           / -> HTTP -> solr
HTTPS -> nginx or traefik ----> HTTP -> cm
                           \ -> HTTP -> cd

The point is that you only manage certificates 1 place instead of in all applications.

BTW solr should not normally be exposed on to the internet :)

[Antonytm]

@pbering Looks like not only me faced with this issue during starting to work with Sitecore images.

May be it make sense to change volume mappings for different configurations to avoid overlapping?

e.g. for xm:
.\data-xm\sql:C:\Data
.\data-xm\solr:C:\Data
for xp:
.\data-xp\sql:C:\Data
.\data-xp\solr:C:\Data

What do you think?

[VipraB]

Good :)

I can't point you to an example but what we are doing (sometime locally and always in upstream environments) is to put a proxy in front that does SSL termination.

Looks like this:

                           / -> HTTP -> solr
HTTPS -> nginx or traefik ----> HTTP -> cm
                           \ -> HTTP -> cd

The point is that you only manage certificates 1 place instead of in all applications.

BTW solr should not normally be exposed on to the internet :)

I am not trying to expose it to the internet but just to run in a secure environement .
So instead of putting the proxy is there any available batch script which can be used as a part of the Dockerfile to create and import the certificates within the docker image this is just for solr for now

[pbering]

@VipraB I do not know if any such scripts exists in the community.

[pbering]

@Antonytm I don't think that is a good idea since the purpose of /tests/ is mainly for those contributing so they easy validate images. It's also used by the community as a starting point and should be copied and modified as needed else where.

We haven't really started to use https://github.com/Sitecore/docker-demo yet but it seems like a better place for what you are asking for.

[michaellwest]

Seems like this is not an issue. Perhaps document that a cleanup is required when switching and then close the issue.