Closed eerhardt closed 3 months ago
I think this is an issue we would service for in an ideal world.
Workaround is to use:
var blobs = builder.AddAzureStorage("Storage")
// Use the Azurite storage emulator for local development
.RunAsEmulator(emulator => emulator.WithImageTag("3.31.0"))
.AddBlobs("BlobConnection");
cc @mitchdenny @joperezr @sebastienros @radical
We hit this earlier too - https://github.com/dotnet/aspire/issues/4646 !
We hit this earlier too - #4646 !
We need a test here, if it broke us twice.
Great find. I agree that we should have a test for this. Is the fix essentially to bump the tag to the new version then? If so we can just do that and ship next month, and folks hitting this can use your workaround.
Repro Steps
In your AppHost:
In your webfrontend project:
F5
hit the
webfrontend/health
endpointExpected results
Healthy
Actual results
Unhealthy
Logs
If we update to image tag
3.31.0
here, the problem goes away:https://github.com/dotnet/aspire/blob/e0552c0bbf3330c2694e72961a97941a5773e139/src/Aspire.Hosting.Azure.Storage/AzureStorageExtensions.cs#L114-L119