Azure Storage ports changing despite using ContainerLifetime.Persistent

[MarcinJuraszek]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

We're using Azure Storage with Emulator and configure it to stay alive between runs using c.WithLifetime(ContainerLifetime.Persistent). Despite that, every time we re-run the AppHost the ports the Emulator is exposing for the app change. This is unexpected and makes things harder than they should be. E.g. we're also using Durable Functions in our project, and use Durable Functions Monitor in VS Code to inspect the inner workings of Durable Task Framework. However, because the ports for the Storage change on every run, the Monitor breaks and we have to re-add a new connection, after getting the new set of ports from Aspire Dashboard.

Expected Behavior

I would expect the Azure Storage connection string exposed by the emulator to stay stable between re-runs of App Host if configured with WithLifetime(ContainerLifetime.Persistent)

Steps To Reproduce

1. Create an App Host with an Azure Storage resource, configure it to use an emulator and set to be persistent between runs:

var storage = builder.AddAzureStorage("storage")
    .RunAsEmulator(c =>
    {
        c.WithDataVolume();
        c.WithLifetime(ContainerLifetime.Persistent);
    });

2. Run the App Host, take note of the Endpoint URLs displayed in the dashboard
3. Stop and re-start the App Host, compare the new Endpoint URLs to the one from previous run

Exceptions (if any)

No response

.NET Version info

No response

Anything else?

No response

[dbreshears]

Let's update to use proxyless for persistent containers.