Docker - Service Control - azureservicebus.init-windows fails on queue creation

Hello. We’re evaluating the containerized version of Service Control for Azure ServiceBus and we’re experiencing problems with the init-container when it tries to create the required queues.

Here’s an output from the docker container (running locally on windows containers):

C:\dev\docker\servicecontrol> docker run -e "ServiceControl/ConnectionString=Endpoint=sb://<my connection string>" -e 'ServiceControl/LicenseText=<?xml version=\"1.0\"...</license>' -v c:/dev/docker/servicecontrol/data/:c:/data/ -v c:/dev/docker/servicecontrol/logs/:c:/logs/ particular/servicecontrol.azureservicebus.init-windows
2021-02-26 09:34:20.1898|1|Info|ServiceBus.Management.Infrastructure.Settings.Settings|No settings found for error log queue to import, default name will be used
2021-02-26 09:34:21.0396|1|Info|ServiceControl.Infrastructure.RavenDB.RavenBootstrapper|Loading Embedded RavenDB license
2021-02-26 09:34:45.5349|1|Info|ServiceControl.Infrastructure.RavenDB.RavenBootstrapper|Index creation started
2021-02-26 09:34:50.7493|1|Info|NServiceBus.LicenseManager|Selected active license from C:\ProgramData\ParticularSoftware\license.xml
License Expiration: 2021-04-19

Unhandled Exception: System.Exception: An error occurred while sending the request.
   at NServiceBus.Transport.AzureServiceBus.QueueCreator.<CreateQueueIfNecessary>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NServiceBus.HostingComponent.<RunInstallers>d__6.MoveNext() in /_/src/NServiceBus.Core/Hosting/HostingComponent.cs:line 59
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NServiceBus.HostCreator.<CreateWithInternallyManagedContainer>d__1.MoveNext() in /_/src/NServiceBus.Core/Hosting/HostCreator.cs:line 96
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Particular.ServiceControl.SetupBootstrapper.<Run>d__1.MoveNext() in /_/src/ServiceControl/SetupBootstrapper.cs:line 64
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Particular.ServiceControl.Commands.SetupCommand.<Execute>d__0.MoveNext() in /_/src/ServiceControl/Hosting/Commands/SetupCommand.cs:line 11
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Particular.ServiceControl.Commands.CommandRunner.<Execute>d__1.MoveNext() in /_/src/ServiceControl/Hosting/Commands/CommandRunner.cs:line 17
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Particular.ServiceControl.Program.<Main>d__0.MoveNext() in /_/src/ServiceControl/Program.cs:line 28
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Particular.ServiceControl.Program.<Main>(String[] args)

It crates the RavenDB folders but can’t seem to create the queue. I’ve tested the same ASB Connection String in ServiceBus Explorer and it works fine.

Any ideas?

Edit: Maybe my container can’t access the network? My docker skills is quite limited, but I will investigate…

//J

Topology creation is taking place over HTTPS. If it’s blocked then creating topology will fail.