How to run docker with netherite backend?

[XBeg9]

I don't see a possible config to change to netherite backend, if it's not possible, I see the dockerfile, could you please suggest steps that I should take to make it work? Thanks

[scale-tone]

Hi @XBeg9 , unfortunately with Netherite DfMon can only work in "injected" mode by now. Means that you would need to install DfMon NuGet package into your running service and then deploy/host it in the same way you deploy/host your service today. And of course, configure auth for you service as needed.

Reason for this limitation is that Netherite does not support "readonly" mode (or at least didn't support it earlier). When an external Functions instance connects to a Netherite-backed Task Hub, it forcibly "joins the party" and tries to process messages, which results in a disaster (because that external instance doesn't have your app's binaries).

Therefore there wouldn't be much sense in making/running a Docker container for DfMon+Netherite, so we don't have that, as of today (although we do have a sample project that demonstrates how to do the plumbing)

But maybe the situation with "readonly" mode in Netherite has advanced since then. @sebastianburckhardt , do you maybe have any further input on this?

[scale-tone]

Added an ARM template for the Netherite backend project, so it is now deployable with

button.

[XBeg9]

This is great! Thanks for quick fixes, I will try to get it deployed to Azure and report back.

[scale-tone]

Also added a Dockerfile, pushed the image as scaletone/durablefunctionsmonitor.netherite and added instructions on how to run it locally.

[XBeg9]

@scale-tone I am getting this issue by running docker with local instructions:

      A host error has occurred during startup operation 'e70f7e98-5abb-4ecb-9016-c9cf2350356e'.
      System.IO.IOException: Function not implemented
         at System.IO.FileSystemWatcher.StartRaisingEvents()
         at System.IO.FileSystemWatcher.StartRaisingEventsIfNotDisposed()
         at System.IO.FileSystemWatcher.set_EnableRaisingEvents(Boolean value)
         at Microsoft.Azure.WebJobs.Script.IO.AutoRecoveringFileSystemWatcher.InitializeWatcher() in /src/azure-functions-host/src/WebJobs.Script/IO/AutoRecoveringFileSystemWatcher.cs:line 64
         at Microsoft.Azure.WebJobs.Script.IO.AutoRecoveringFileSystemWatcher..ctor(String path, String filter, Boolean includeSubdirectories, WatcherChangeTypes changeTypes, ILoggerFactory loggerFactory) in /src/azure-functions-host/src/WebJobs.Script/IO/AutoRecoveringFileSystemWatcher.cs:line 43
         at Microsoft.Azure.WebJobs.Script.Eventing.File.FileWatcherEventSource..ctor(IScriptEventManager eventManager, String source, String path, String filter, Boolean includeSubdirectories, WatcherChangeTypes changeTypes, ILoggerFactory loggerFactory) in /src/azure-functions-host/src/WebJobs.Script/Eventing/File/FileWatcherEventSource.cs:line 28
         at Microsoft.Azure.WebJobs.Script.WebHost.FileMonitoringService.InitializeFileWatchers() in /src/azure-functions-host/src/WebJobs.Script.WebHost/FileMonitoringService.cs:line 157
         at Microsoft.Azure.WebJobs.Script.WebHost.FileMonitoringService.StartAsync(CancellationToken cancellationToken) in /src/azure-functions-host/src/WebJobs.Script.WebHost/FileMonitoringService.cs:line 93
         at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
         at Microsoft.Azure.WebJobs.Script.WebHost.WebJobsScriptHostService.UnsynchronizedStartHostAsync(ScriptHostStartupOperation activeOperation, Int32 attemptCount, JobHostStartupMode startupMode) in /src/azure-functions-host/src/WebJobs.Script.WebHost/WebJobsScriptHostService.cs:line 311```

[scale-tone]

Looks like you've run into this issue. Seems to be Mac-specific, and no workaround suggested so far :(
Can only suggest either to run the backend locally or deploy it to Azure. It is also always possible to run the container as e.g. Azure Container Instance.