Docker: "The API version 2025-01-05 is not supported by Azurite."

[skarum]

Using Azurite docker image and upgrading from Azure.Storage.Blobs (.NET) version 12.19.1 to 12.23.0 I get the following error

Azure.RequestFailedException : The API version 2025-01-05 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. 
RequestId:58ccc424-d7c8-4e28-a6c6-09d991282930
Time:2025-02-26T13:09:03.924Z
Status: 400 (The API version 2025-01-05 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. )
ErrorCode: InvalidHeaderValue

Content:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Error>
  <Code>InvalidHeaderValue</Code>
  <Message>The API version 2025-01-05 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. 
RequestId:58ccc424-d7c8-4e28-a6c6-09d991282930
Time:2025-02-26T13:09:03.924Z</Message>
</Error>

Headers:
Server: Azurite-Blob/3.28.0
x-ms-error-code: InvalidHeaderValue
x-ms-request-id: 58ccc424-d7c8-4e28-a6c6-09d991282930
Date: Wed, 26 Feb 2025 13:09:03 GMT
Connection: keep-alive
Keep-Alive: REDACTED
Transfer-Encoding: chunked
Content-Type: application/xml


  Stack Trace: 
ContainerRestClient.CreateAsync(Nullable`1 timeout, IDictionary`2 metadata, Nullable`1 access, String defaultEncryptionScope, Nullable`1 preventEncryptionScopeOverride, CancellationToken cancellationToken)
BlobContainerClient.CreateInternal(PublicAccessType publicAccessType, IDictionary`2 metadata, BlobContainerEncryptionScopeOptions encryptionScopeOptions, Boolean async, CancellationToken cancellationToken, String operationName)
BlobContainerClient.CreateIfNotExistsInternal(PublicAccessType publicAccessType, IDictionary`2 metadata, BlobContainerEncryptionScopeOptions encryptionScopeOptions, Boolean async, CancellationToken cancellationToken)
BlobContainerClient.CreateIfNotExistsAsync(PublicAccessType publicAccessType, IDictionary`2 metadata, BlobContainerEncryptionScopeOptions encryptionScopeOptions, CancellationToken cancellationToken)
ImportDataFromKonditool_Should.CreateContainers() line 47
ImportDataFromKonditool_Should.ImportJob_ValidInput_MovesFileToImportedContainer() line 63
--- End of stack trace from previous location ---

This happens with latest tag.

Looking at dockerhub (https://hub.docker.com/r/microsoft/azure-storage-azurite) it looks like the image have not been updated in 10 months, but the latest release (3.33.0) is only 4 months old (and have the release note Bump up service API version to 2025-01-05)

Is the docker image not updated in the same cadence as the normal executable?

[blueww]

Hi @skarum,

You should not be using the real latest docker image 3.33.0.

The "latest" Azurite image you download before 3.33.0 release might cached on you local machine, so when you run "latest" Azurite docker image, you actually is running a before release.
Please remove the "latest" Azurite docker image from you machine, and try again. Or you can just download Azurite docker image with version 3.33.0, and run from 3.33.0 image.

You can also run Azurite with parameter "--skipApiVersionCheck" to skip API version check in Azurite.

BTW, the doc show on https://hub.docker.com/r/microsoft/azure-storage-azurite) normally not change when a new Azurite not change the way to run Docker image. But if you check More history tags⁠, you will see the 3.33.0 release.

[skarum]

Thanks for the reply, it helped me figure out what was wrong in my usage.

I had tried with the 3.33.0 label, but had the same issues.

Turned out the "--skipApiVersionCheck" did the trick. I had tried it, but wrongly. Using TestContainers it needs to be like this

new AzuriteBuilder()
    .WithImage("mcr.microsoft.com/azure-storage/azurite:3.33.0")
    .WithCommand("--skipApiVersionCheck")
    .Build();

Found here: #2432 (comment)

[balbany]

Hi @skarum,

You should not be using the real latest docker image 3.33.0.

The "latest" Azurite image you download before 3.33.0 release might cached on you local machine, so when you run "latest" Azurite docker image, you actually is running a before release. Please remove the "latest" Azurite docker image from you machine, and try again. Or you can just download Azurite docker image with version 3.33.0, and run from 3.33.0 image.

You can also run Azurite with parameter "--skipApiVersionCheck" to skip API version check in Azurite.

BTW, the doc show on https://hub.docker.com/r/microsoft/azure-storage-azurite) normally not change when a new Azurite not change the way to run Docker image. But if you check More history tags⁠, you will see the 3.33.0 release.

Thanks @blueww - this was my issue. Just commenting to note that skipping the API version check wasn't necessary once the actual latest docker image was in play.