Conflict between revisions using .WithDataVolume() and Qdrant integration in Azure Container Apps

[snavarropino]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When integrating Qdrant in Aspire using .WithDataVolume():

var qdrant = builder
    .AddQdrant("qdrant")
    .WithEndpointProxySupport(proxyEnabled)
    .WithDataVolume();

and deploying via azd with an Azure DevOps pipeline to Azure Container Apps, everything works fine initially. Aspire automatically creates a Storage Account and maps a file share into the container.

However, during subsequent deployments, the new revision sometimes fails to become active. Logs indicate that multiple containers are competing for access to files in the mounted volume.

Question:
Is there a recommended way to avoid this issue?

Thanks in advance for any guidance!

Expected Behavior

New revision works

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version info

.NET 9

Anything else?

No response

[snavarropino]

A forgot to attach the error, is this:

2025-07-03T12:34:56.499752Z ERROR qdrant::startup: Panic occurred in file /qdrant/lib/collection/src/shards/replica_set/mod.rs at line 300: Failed to load local shard "./storage/collections/skdocuments/0": Service internal error: RocksDB open error: IO error: No such file or directory: while unlink() file: ./storage/collections/skdocuments/0/segments/01e9682c-caf7-4e9d-ab7f-30d473ae5b46/LOG.old.1751546045376042: No such file or directory

It happens randomly on deployments resulting in the new revision to fail