The API version 2024-05-04 is not supported by Azurite. Please upgrade Azurite to latest version and retry. If you are using Azurite in Visual Studio, please check you have installed latest Visual Studio patch. Azurite command line parameter "--skipApiVersionCheck" or Visual Studio Code configuration "Skip Api Version Check" can skip this error.

Getting the following azurite error. I upgrade Azurite and still the same message:
The API version 2024-05-04 is not supported by Azurite. Please upgrade Azurite to latest version and retry. If you are using Azurite in Visual Studio, please check you have installed latest Visual Studio patch. Azurite command line parameter "--skipApiVersionCheck" or Visual Studio Code configuration "Skip Api Version Check" can skip this error.

Ran into this today and had to poke around in their sample app to figure out why it worked and my code didn't.

If you target Azure.Storage.Blobs version 12.19.1 instead of 12.20.0 then it avoids this error. That package is a dependency of Aspire.Azure.Storage.Blobs. That is my workaround for now at least.

This work around only works for the previous version of Aspire. The latest (8.0.2) requires Azure.Storage.Blobs >= 12.20.0. Is there another work around for 8.0.2?

Facing the same issue.

They released 8.0.2 after my previous comment. I'm sure this will be updated eventually as well but they released a new version of Azurite that supports this API version(3.30.0).

The RunAsEmulator call hardcodes version 3.29.0 inside that extension method. That is suppose to be fixed though.

    storage.RunAsEmulator(c => c.WithImageTag("3.30.0"));

That should download the new azurite container and start it up as usual.

Jordan Zaerr (@JordanZaerr)

As Jordan Zaerr (@JordanZaerr) said, just use Azure.Storage.Blobs version 12.19.1 and it will work. 😊

They released 8.0.2 after my previous comment. I'm sure this will be updated eventually as well but they released a new version of Azurite that supports this API version(3.3.0).

The RunAsEmulator call hardcodes version 3.29.0 inside that extension method. So I just call that function again with the new version...
storage.RunAsEmulator()
    .WithAnnotation(new ContainerImageAnnotation
    {
        Registry = "mcr.microsoft.com",
        Image = "azure-storage/azurite",
        Tag = "3.30.0"
    });
That should download the new azurite container and start it up as usual.

This worked with 8.0.2. Thank you!

Zach Barrier (@zbarrier)

Zach Barrier (@zbarrier) I edited my comment because in the PR I linked I found a cleaner way to do the same thing.

FYI with the release of 8.1.0 today you need to use an Azurite docker container with the 3.31.0 tag supporting "2024-08-04" api version.

var storage = builder.AddAzureStorage("storage").RunAsEmulator(c => c.WithImageTag("3.31.0"))

Hi Folks, with the new GA version of Azure Storage 2.0.0, it is only compliant with 12.20.0 version of Azure.Storage.Blobs, in this version the mismatch issue is not getting resolved. What should we do here?

Added to this, we need to use blob uri of azurite instead of connection string, as part of the new methods introduced in azure storage 2.0.0

fix: microsoft/aspire#4646

When using these components:

Aspire.Azure.Storage.Blobs / Aspire.Hosting.Azure.Storage version 8.2.1
docker image azure-storage/azurite:3.31.0

The error is now

The API version 2024-11-04 is not supported by Azurite

In my opinion it is a new symptom of the issue reported above; if you feel it should be a new issue, please convert this comment into an issue.

Part of me thinks we should just pass skipVersiobcheck by default

fix: microsoft/aspire#4646

Sébastien Ros (@sebastienros)

Sébastien Ros (@sebastienros) can you look at this?

Why not use the 'latest' image tag? Solved the issues for me.

        var blobs = builder.AddAzureStorage("storage")
            .RunAsEmulator(c => c
                .WithDataVolume()
                .WithImageTag("latest")
             )
            .AddBlobs("blobs");

I have submitted a PR to add --skipApiVersionCheck by default. Thanks for testing it.

This is fixed in 9.1, in ~an hour so you can try a build here and let us know if we missed anything https://github.com/dotnet/aspire/blob/main/docs/using-latest-daily.md 😄

fix: microsoft/aspire#4646

Navigation Menu

Repository navigation

5 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Description

Activity

JordanZaerr commented on Jun 27, 2024

zbarrier commented on Jul 2, 2024

for-shariq commented on Jul 2, 2024

JordanZaerr commented on Jul 2, 2024

VasilisPlavos commented on Jul 2, 2024

zbarrier commented on Jul 2, 2024

JordanZaerr commented on Jul 2, 2024

NapalmCodes commented on Jul 24, 2024

shivamverma-ms commented on Aug 12, 2024

5 remaining items

hansmbakker commented on Oct 16, 2024

davidfowl commented on Oct 16, 2024

davidfowl commented on Jan 10, 2025

kwaazaar commented on Jan 10, 2025

sebastienros commented on Jan 24, 2025

davidfowl commented on Jan 24, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions