Unhealthy Azure Storage Emulator on some devices

[Yarkane]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

On some configurations, we have an issue running the Azurite Azure Storage Emulator via Docker. It seems to launch without any issue ("Azurite Blob service is starting at ..."), but the other aspire services cannot start after it ("Emulator start up probe unsuccessful"). We got it working on similar configurations but not on specific ones.

For example, running an Event Hub emulator over the Azure Storage emulator : the Event Hub emulator never starts as the Azure Storage emulator start up probe is always unsuccessful.

Expected Behavior

As I instanciate a Azure Storage Emulator and then a Event Hub emulator, the two containers should start one after the another.

Steps To Reproduce

This code worked on some devices and not on another :

var eventHub = () => builder
	.AddAzureEventHubs("eventhubnamespace")
	.RunAsEmulator(x => x.WithDataBindMount().WithLifetime(ContainerLifetime.Persistent))
	.AddEventHub("eventhub");

Please note that the issue is not specific to Event Hub as the Blob Storage emulator have the same issue :

var blobs = () =>
{
	var storage = builder
					.AddAzureStorage("azurestorage")
					.RunAsEmulator(x => x.WithLifetime(ContainerLifetime.Session).WithImageTag("3.33.0"));
	return storage.AddBlobs("blobstorage");
};

Exceptions (if any)

No issue in the Azurite pod container :

But crash at launch for the Event Hub emulator :

.NET Version info

• ASP.NET Core version : 9.0.0
• Aspire version : 9.0.0 (issue reproduced in 9.2.x too)
• We use Docker Desktop as the backend for the containers of Aspire : v4.40.0
• We use WSL as the backend for Docker Desktop :

Anything else?

You will maybe have some ideas about this bug, I know that it is hard / impossible to reproduce, but maybe have you already seen something like that ? We already got through basic debugging with Docker Desktop (reset, etc).

Have a good day and thank you for reading !