Host ServiceControl on Azure Container apps

,
1

Hej everyone,

We’re running ServiceControl, ServicePulse, RavenDB, and Audit as Azure Container Apps.

We’ve noticed that after deploying a new revision of the container apps, the RavenDB container often ends up in a faulty state with the following error:

Cannot open database because RavenDB was unable to create file lock on ...

The mapped SMB volume does contain the lock file, but even manually, we’re unable to delete it. This makes me suspect that the container isn’t shutting down cleanly during deployment, leaving the lock file behind.

Is anyone else running ServiceControl in Azure Container Apps? Any tips or tricks to ensure clean shutdowns or avoid this issue with RavenDB?

Appreciate any insights!

Kind regards,
Jonathan

2

Hi @jonathan.maes,

RavenDB does not support SMB volumes , which explains the lock file issues you’re seeing. The container likely isn’t shutting down cleanly because RavenDB can’t properly manage file locks on that type of volume.

Here are a couple of relevant references for more details:

To avoid these issues, consider using supported storage options or deployment targets that are compatible with RavenDB’s requirements.

Hope this helps!

Best regards,

The Particular Software Support Team