-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot add --skipApiVersionCheck when using testcontainers #2432
Comments
@ShaharPrishMSFT For how to input the parameter with the API you shows above, this is out of Azurite scope. You might can contact the API owner to get it. |
If you are using Testcontainers you should take a look on this https://java.testcontainers.org/features/commands/ this is how you pass commands at least this is what its documented there. This code example may help you a bit since we are using GenericContainers
|
@ShaharPrishMSFT is it possible your private readonly AzuriteContainer _azuriteContainer = new AzuriteBuilder()
.WithImage("mcr.microsoft.com/azure-storage/azurite:latest")
.WithCommand("--skipApiVersionCheck")
.Build(); |
Which service(blob, file, queue, table) does this issue concern?
Blobs
Which version of the Azurite was used?
Latest - there's no version listed here: https://hub.docker.com/r/microsoft/azure-storage-azurite, but that's what I am using.
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
DockerHub
What's the Node.js version?
What's inside the image
What problem was encountered?
Cannot figure out how to pass in --skipApiVersionCheck
Steps to reproduce the issue?
If possible, please provide the debug log using the -d parameter, replacing <pathtodebuglog> with an appropriate path for your OS, or review the instructions for docker containers:
Getting the following error:
Please be sure to remove any PII or sensitive information before sharing!
The debug log will log raw request headers and bodies, so that we can replay these against Azurite using REST and create tests to validate resolution.
Have you found a mitigation/solution?
No - tried adding it via WithEntryPoint and that didn't work either.
The text was updated successfully, but these errors were encountered: