-
Notifications
You must be signed in to change notification settings - Fork 362
Closed
Labels
alignmentAlignment between Azurite with Azure Storage productionAlignment between Azurite with Azure Storage productionfeatureparityTracking issues for catching up feature parityTracking issues for catching up feature parity
Description
Having just updated to the latest version (12.25.0) of Azure.Storage.Blobs, I'm receiving the following error in my integration tests which use Testcontainers.Azurite.
Azure.RequestFailedException : The API version 2025-07-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:6c06dd65-2899-49d7-a023-ae6ab818440d
Time:2025-07-15T08:08:31.066Z
Status: 400 (The API version 2025-07-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-07-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:6c06dd65-2899-49d7-a023-ae6ab818440d
Time:2025-07-15T08:08:31.066Z</Message>
</Error>
Headers:
Server: Azurite-Blob/3.34.0
x-ms-error-code: InvalidHeaderValue
x-ms-request-id: 6c06dd65-2899-49d7-a023-ae6ab818440d
Date: Tue, 15 Jul 2025 08:08:31 GMT
Connection: keep-alive
Keep-Alive: REDACTED
Transfer-Encoding: chunked
Content-Type: application/xml
Stack Trace:
at Azure.Storage.Blobs.ContainerRestClient.CreateAsync(Nullable`1 timeout, IDictionary`2 metadata, Nullable`1 access, String defaultEncryptionScope, Nullable`1 preventEncryptionScopeOverride, CancellationToken cancellationToken)
at Azure.Storage.Blobs.BlobContainerClient.CreateInternal(PublicAccessType publicAccessType, IDictionary`2 metadata, BlobContainerEncryptionScopeOptions encryptionScopeOptions, Boolean async, CancellationToken cancellationToken, String operationName)
at Azure.Storage.Blobs.BlobContainerClient.CreateIfNotExistsInternal(PublicAccessType publicAccessType, IDictionary`2 metadata, BlobContainerEncryptionScopeOptions encryptionScopeOptions, Boolean async, CancellationToken cancellationToken)
at Azure.Storage.Blobs.BlobContainerClient.CreateIfNotExistsAsync(PublicAccessType publicAccessType, IDictionary`2 metadata, BlobContainerEncryptionScopeOptions encryptionScopeOptions, CancellationToken cancellationToken)
I'm able to work around the issue following the example here, I'm raising this to highlight that the latest release of Azurite has fallen behind the real API.
new AzuriteBuilder()
.WithCommand("--skipApiVersionCheck")
.Build();ThumbGen, spanglerco, leniency, konradmalik, jchannon and 23 more
Metadata
Metadata
Assignees
Labels
alignmentAlignment between Azurite with Azure Storage productionAlignment between Azurite with Azure Storage productionfeatureparityTracking issues for catching up feature parityTracking issues for catching up feature parity