Automatic detection of running Azure instances not working

[dluc]

Storage Explorer Version

1.38.0

Regression From

No response

Architecture

arm64

Storage Explorer Build Number

No response

Platform

All

OS Version

macOS latest

Bug Description

I use Azurite through .NET Aspire, when running the code locally. .NET Aspire starts Azurite docker image using random ports, e.g.

cdfb050ec13d   mcr.microsoft.com/azure-storage/azurite:3.34.0   "docker-entrypoint.s…"   2 hours ago     Up 2 hours     127.0.0.1:61082->10000/tcp, 127.0.0.1:61080->10001/tcp, 127.0.0.1:61081->10002/tcp   azurestorage-82d80060

The storage explorer apparently detects the instance, but does not map the ports correctly, so it's not possible to use the auto discovery.

The old way, creating manual connections entering the random port selected by Aspire, that works fine:

Also, from time to time this appears, even if Azurite is running in the background:

Steps to Reproduce

1. Deploy Azurite using .NET Aspire:

var storage = builder.AddAzureStorage("azurestorage");

if (builder.ExecutionContext.IsRunMode)
{
    storage.RunAsEmulator(o => { o.WithLifetime(ContainerLifetime.Persistent); });
}

2. Start Aspire AppHost locally.
3. Try to connect to Azurite with Storage Explorer

Actual Experience

Fails to connect. Requires users to create connections manually, finding the random port selected by Aspire.

Expected Experience

Should work

Additional Context

No response

[craxal]

@dluc What ports is Storage Explorer detecting? You can see this by clicking on the tree node representing the emulator connection and examining the properties.

Can you share the output of the following command:

docker -v
docker ps --format json
docker inspect <container ID> --format json

[craxal]

Closing due to inactivity. If this still an issue, please reply with answers to the above questions, and we can revisit.